Forum upgrade?

[MarkMLl]

Maybe it decided that all people who don’t have the latest greatest browser  shouldn’t have the privilege of reportIng bugs.

You've refused to tell us what you're running.

MarkMLl

[Aruna]

Maybe it decided that all people who don’t have the latest greatest browser  shouldn’t have the privilege of reportIng bugs.

You've refused to tell us what you're running.
MarkMLl

Last couple of lines on this post tell's us :

Code: Text  [Select][+][-]

1. using win 7
2. Lazarus 2.0.12 r64642 FPC 3.2.0 x86_64-win64-win32/win64
3. « Last Edit: September 05, 2024, 06:39:17 pm by Joanna »

May not necessarily be the system(s) she is on at this moment in time :-)

[MarkMLl]

Last couple of lines on this post tell's us :

Shouldn't be necessary to go hunting like that BUT: browser version? screen size?

I /might/ /possibly/ fire up an old laptop with- by definition- an old browser and limited screen size to look at something else shortly, which would give me an opportunity to try the bug reporter.

MarkMLl

[rvk]

Last couple of lines on this post tell's us :

That doesn't tell which browser (which is important for accessing gitlab).

If javascript isn't the problem then it could be just a minor issue which can be fixed without much trouble.

[Joanna]

Maybe it decided that all people who don’t have the latest greatest browser  shouldn’t have the privilege of reportIng bugs.

You've refused to tell us what you're running.

MarkMLl

I guess I didn’t... However gitlab should not be requiring me to have a specific browser in order to use it. That is my point. Another thing I’d like to say is there is not much cohesion in this community if nobody has reported the bugs that I discovered, knowing that I am unable to access the bug tracker. I don’t even care if someone else gets credit for reporting the bugs I discovered but nope not happening. Apparently, berating me about what my operating system and web browsers are is far more fun that improving Lazarus and fpc. How toxic..

Also I’m curious why the mantis bug tracker was discontinued?

[rvk]

I guess I didn’t... However gitlab should not be requiring me to have a specific browser in order to use it. That is my point.

They don't. Where do you see that a specific browser is required?????

Only javascript is required.

That you don't see the page (with javascript enabled) is due to some other problem.
That's why we where trying to find out what your problem is exactly.

(That you attach the "gitlab doesn't accept my browser" is just your interpretation of the fact it doesn't work for you.)

[Joanna]

Rvk some websites will tell you they don’t like your browser. Other websites just will be unusable. I am unable to use gitlab on a webrowser that works fine for other sites that have javascript.

But don’t worry maybe gitlab will work better if enough people scream insults at me 

[rvk]

Rvk some websites will tell you they don’t like your browser.

I take it that gitlab doesn't prompt you which such message, does it?

So it should work correctly in that case.
If you want it to work you might want to provide more information if you want help.
We might be able to search gitlab forum for the solution or ask there what's the problem might be.

Otherwise... I hope this forum upgrades soon too.
(If you get locked out, then you have no way to ask for help here, because you don't have access. So it's better to get ahead of these things instead of hoping there is never an upgrade.)

[Martin_fr]

No personal insult please.

[Martin_fr]

I read somewhere that other people had issues with GitLab, because they had certain browser feature disabled (by enabling some tracking protection or similar).

And apparently (at that time) Gitlab uses (or used?) those features to establish that the user has what "they believe to be an actual web-browser, rather than a bot". I don't know how well that works, or how much it affects real users... (always a danger, if you try to fight trolls SCNR).
So if some browser does not support those things...

I have (long ago, and then there were less browsers than today) be involved into running some websites. The amount of work it takes to just support even only the "popular" browsers correctly... And a great many users wont use a websites if they don't look and behave "nice". That is not just JS. Download the css from any bigger site... It's usually massive. And loaded with browser specific extensions... But, if sites don't do it, (many) users go elsewhere. So loosing "purists" is just less of a loss, sadly.


Mantis: AFAIK No one wanted to do the maintenance work.

Forwarding bugs...

I haven't searched for where they were mentioned (haven't even checked this thread)...

But it is always problematic. Doing so, then means to have to reverse forward all and any question that  developers ask on the bug. I guess not many people t want to play valet.

[rvk]

I read somewhere that other people had issues with GitLab, because they had certain browser feature disabled (by enabling some tracking protection or similar).

I have Brave browser. It already blocks a lot of these tracking items.
(which I can see if I go into developer mode via F12)

I don't have problems in gitlab. But it could be some other related issue (pihole, which I also run, or something else).

@Joanna You could look in F12 to see if you can figure out what makes the site crap out.
Via console and network tab you often see error messages which can help.

[Joanna]

Rvk some websites will tell you they don’t like your browser.

I take it that gitlab doesn't prompt you which such message, does it?

So it should work correctly in that case.
If you want it to work you might want to provide more information if you want help.
We might be able to search gitlab forum for the solution or ask there what's the problem might be.

Otherwise... I hope this forum upgrades soon too.
(If you get locked out, then you have no way to ask for help here, because you don't have access. So it's better to get ahead of these things instead of hoping there is never an upgrade.)

There is no way to win the upgrade treadmill.. oops your computer is too old to upgrade .. go buy a new computer! game. I’m not even going to try. 
It seems that gitlab prefers people who use certain operating systems over others.
I managed to view the bug tracker on gitlab, unfortunately I’m no longer in the mood for making any bug reports. The reason should be obvious.

[rvk]

It seems that gitlab prefers people who use certain operating systems over others.

Again... that's your interpretation.
"It doesn't work so it must be that they don't support my computer"

That's not how it works.
Yes it could be that your browser (or computer) is too old.
But there is no way of telling what's the problem if you don't give us details.

That just like saying "My program doesn't start"... without telling us anything else.
" Yeah... the computer doesn't like you... that's why it doesn't start your program  "

[Joanna]

I’d rather not discuss the details of my computer on a public forum.
Suffice it to say it was the operating system not the age of the browser.

There is a good chance that my computer doesn’t like me. 

[Martin_fr]

I just run a test (from an old VM / normally not used to connect to the internet): On XP, neither Firefox nor I-Explorer can display Gitlab. But then both of those browsers did not have updates for a long time, as the makers don't supply updates for XP any more. So well possible that if I downgraded those browsers on my Win10 machine I would also get issues.

The other thing is, that XP afaik doesn't have/get the latest master certificates. So some sites wont work as there cert can't be verified. And also they may not have the latest encryption algorithms avail... Though, there may be browsers who bring in such stuff on their own, rather than relying on the OS.


I don't know what old OS exists that still get at least security updates (against OS exploits). Because any OS that doesn't, IMHO doesn't count when it comes to "should a website support it". Better if a website does not, as such OS should not be used for internet access. Even if the browser handles as much as it can outside the OS, things like the TCP/IP stack could still have exploitable vulnerabilities. Those machines may be good for certain offline work though.