What is it with web developers breaking things? It's as if they want to reinvent the wheel time after time. I understand that stagnation is not good, but we've had collapsible menus and fade/slide animations for years. Why complicate them to such a degree that they completely break functionality when our JavaScript support is a little older? It's not like we don't have JavaScript; we do, but it's just not really up-to-date anymore. @Ryan Bremer, is this specific Github issue addressable with a userscript?
Regardless, I've been experimenting with injecting a local polyfill package (from Cloudflare) in tab-content.js, but I haven't had any success so far. I think I'm injecting it too late in the loading processes. But loading this into every tab, I'm unsure of the effects on performance.
@GA204 @f54da, any updates on this? I'm quite new to modern JavaScript (anything beyond basic JS; my personal website is just plain HTML/CSS, and the only JS included is a third-party frame link script which updates the URL for convenience), but I'm willing to dedicate time to this. I just need a plan of approach, as I'm not entirely sure where to even start, especially since my initial experiments proved less than fruitful.
P.S. There's a GitHub issue related to this here.
It been ridiculous with GitHub, they really put efforts to have it broken. For example, I could not view plain text files in repos last few days. (That worked not long ago, broken just now.) Issues in repos do not work for ages.
Besides, not just on PowerPC; GitHub does not work properly in Palemoon on Catalina (!). And even in Safari it is super-slow (no hyperbole, it is like opening web in 2000). Either developers there are just b*****t bad – or deliberately break things.
And this is the website which could have been usable in plain text!