There was a period of time when sites pretty much worked everywhere. In the last five years or so, the number of sites that only work in Chrome was risen precipitously. It's either malice or incompetence, and I have no trouble believing either.
The general push towards a single engine is just undeniable at this point. Whoever controls the browser, controls the web.
What are some of the glitches? I'm curious if I've ran into any of them.
But all things considered that's pretty minor
Type a long blurb into a text input widget e.g. a comment on a pull request. The text just bounces up and down as you type. I've noticed this with whatever the extended support version of Firefox (macos 10.14) is and with the current Firefox (macos 14.1). To be fair GH renders widgets partially off screen with whatever version of Safari comes with macos 10.14 There is no more static text on GH so if you go back further than that (or have javascript disabled) nothing renders at all.
There's no issue tracker (because why would there be?) but there was a discussion thread. Last I saw someone posted detailed steps to reproduce a search bug and the GH response was to lock the discussion thread.
Repository settings have a whole lot of knobs and toggles that don’t save or remain disabled unless you manage them from a chromium-something.
I agree that while it doesn’t need to be targeted at specific agents, the fact that they don’t spend the time to test their things on other agents is saying enough.
I fear you're right. Evidence: IE6. But eventually we will come out the other side.
1. At first it was “works best with Netscape Navigator”
2. Then it was the same with IE
3. Now it’s Chrome.
With one notable exception of Google Meet, which consistently tended to fail on anything but Chrome.