From: "Anna V." <cyber+gentoo@sysrq.in>
To: gentoo-project@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-project] gitlab accessibility
Date: Fri, 15 Jul 2022 13:09:31 +0500 [thread overview]
Message-ID: <YtEguyXqd4NanK/q@sysrq.in> (raw)
In-Reply-To: <80b169d1890fb8fad87a80728caa87688d8540f1.camel@gentoo.org>
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/
next parent reply other threads:[~2022-07-15 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YtCIyloDJDRRopAY@linux1.home>
[not found] ` <80b169d1890fb8fad87a80728caa87688d8540f1.camel@gentoo.org>
2022-07-15 8:09 ` Anna V. [this message]
2022-07-15 22:01 ` [gentoo-dev] Re: [gentoo-project] gitlab accessibility William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YtEguyXqd4NanK/q@sysrq.in \
--to=cyber+gentoo@sysrq.in \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox