On 2022-07-15 09:09, Michał Górny wrote:
On Thu, 2022-07-14 at 16:21 -0500, William Hubbs wrote:
Hey all,
I was on vacation when the issues were brought up, but I want to start a new thread about this.
I will quote the sections from the messages on the previous thread I am referring to.
mgorny:
I would really prefer if someone worked on the GitLab accessibility issues before someone tried to do that. Like, made GitLab something
more than a blank site on less-than-state-of-art web browsers.
I don't know which browsers you are talking about. I personally use
chrome and it isn't a blank page. I'm sure it probably works on firefox
as well. I have briefly checked Edge and it is fine there.
I think you need to be more specific about the browsers you are talking about. Also, if you are a web developer, you might want to open MR's for gitlab to get this fixed if you can.
I'm talking of browsers without ECMAScript, particularly text browsers.
On GitHub, things obviously aren't perfect but I can at least find
a file in the repository and view its contents. On GitLab, the file
list is simply not there.
You can always `git clone` the repo to view its files. But non-standard features (like "merge requests" and CI) indeed require using either:
* a browser with bleeding edge JS support (because everyone uses latest
Chrome and Firefox and polyfills/babel are for losers who don't use experimental features in production)
* OR custom CLI utilies (btw, can you point me on some I can use? like dev-vcs/hub for GitHub -- I have no desire to interact with their heavy
and slow[0] web application).
[0]:
https://forgeperf.org/
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)