Iām seeing this too. As always with broken pages the question is if they did something silly, or the browser is just too old for something theyād reasonably expect to use. I wouldnāt really call either of those issues a (separate) bug though.
Github is getting progressively worse since the Microsoft takeover: constant nagging, previously accesible features turning āproā, pointless āimprovementsā and, yes, their website getting fancier and fancier to the point itāll probably only work on Edge (or, Chromium-based browsers) at some point.
Iām actually surprised a command line git clone still works most of the time.
I can reproduce (or at least produce a similar issue) in a desktop Mozilla browser by browsing to github and disabling all javascript (through uBlockOrigin).
Like invidious, meaning a lighter web frontend? No. One should seriously consider simply using a different public git server. Alternatives abound. Many gitlab instances* for example. Or Gitea, gogs, etc. - git itself also features a web server/UI.
Ah, Iāve been silently cursing this for ages. BUT, the fact is, on my IPv6 only virtuals, github canāt be reliably (if at all) contacted, so Iām not so surprised they canāt create web pages. Canāt do dual stack ip while offering 50 % faster coding. Ah, ha.