You must log in or # to comment.
So TL:DR, chrome is like internet explorer was before firefox. It does some things outside the standard, and because it’s the modern day “default”. sites sloppily code to work with it, and other browsers are left carrying the bag because if tiktok doesn’t work on firefox, people will view that as a firefox problem. Even if firefox is the one actually following the standards when tiktok and chrome aren’t.
Shit like this will continue to happen until governments start enforcing interoperable open standards and resume enforcing antitrust laws, which were, in practice, suspended for a long time, for whatever reason.
Reminds me of how much effort GPU driver devs put in to fixing completely borked games that don’t follow spec / violate apis / rely on undocumented or undefined behaviour / etc
It’s a really dumb situation…
I think similar how the EU adopted the USB-C as mandatory standard for charging, it should force other industries, including software vendors, to follow commonly defined standards.
In case of browsers that is Chrome using it’s de facto monopoly to force other browser to rush to catch up with their custom crap. Yes, as a side effect that would also break a lot of existing webpages because they rely heavily on browser bending over backwards to accommodate sites serving effectively broken HTML i.e. but in the long term this would improve the internet as a whole.
The industry needs to shift to identifying html, css, and JavaScript versions in browser headers instead of which rendering engine. Saying “I support these versions of these standards” instead of “I’m chromium”.
It’s been a problem since day one. Maybe have some sort of independent certification for each browser to pass before being able to declare that it supports a particular version.
You’d have to indicate “I also support these optional bits” for this to really work, which would lead to truly massive headers.
I prefer the idea of slapping people who put up pages that cater to Chrome rather than reading and following the standards upside the head with a large dead fish. People who write faulty WYSIWYG web design software get smacked once for every bad site deployed with their help.
There shouldn’t be any “optional bits”. Thats part of the problem. Either it’s part of a standard or it’s not. Either you meet the standard for that version number, or you don’t.
