> many of these are in fact not a standard according to W3C and should not be implemented in any browser until it is.
That's not exactly how standards work. A browser (or anyone) comes up with a spec, a browser can ship it (to test the waters in an origin-trial, to gain traction if they believe in it), and the standard (often) comes after the fact:
"Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. [...] In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread."
> A browser (or anyone) comes up with a spec, a browser can ship it (to test the waters in an origin-trial, to gain traction if they believe in it), and the standard (often) comes after the fact:
1. Google often doesn't bother even with a spec. Or it creates a semblance of a spec, throws it up on a googler's Github account, ships it and advertises it as "emergin standard" on web.dev
I mean, the status of many (if not most) of the APIs that these sites push are literally "napkin scribble, not on any standards track".
2. Google pushes a lot of APIs quickly into production even if there's a very explicit open objection from other browser vendors (any objections are routinely ignored: from general objections to the shape of APIs to whether it can even be implemented outside Chrome).
3. I wouldn't really quote Alex Russel on anything related to standards, as he is responsible (directly or indirectly) for quite a few of those because of his work on Web Components. E.g. Constructable Stylesheets were shipped in Chrome because Google's own lit project needed them. They shipped it in production when the design contained a trivially triggered race condition, it was called out, and Google completely ignored it because "users want it" or something.
4. Browser vendors quite literally agreed not push incompatible only-exists-in-one-browser shit after the browser wars. The whole standards process is designed to minimize this. Well, Chrome is the dominant browser, so of course they shit all over the process, and quite a few people cheer them for that.
Internet Explorer in the 2000s: shits out a bunch of own non-standard crap, people boo them
Chrome in the 2010s-2020s: shits out a bunch of own non-standard crap, people cheer and blame other browsers for not implementing this crap because... Google is "the champion of open web" or some such bullshit.
3. So what, bugs can be fixed. It's nowhere near as abusive as what Apple does by forcing Safari on every iOS browser.
4. You think the "browser wars" are over? Apple's actions clearly indicate the war is on, and they've selected the nuclear option of forbidding any other browser on their platform.
>Internet Explorer in the 2000s: shits out a bunch of own non-standard crap, people boo them
Did people "boo" XMLHTTPRequest? Because it actually revolutionized the web, and people cheered it.
When you deliberately ignore what Google is doing, every view that is not praising Google's take over of the web is skewed.
> So what, bugs can be fixed.
No. Not on the web they can't. Once it's shipped, people depend on the functionality. That is why we're stuck with so many crappy unfixable APIs in the platform.
> Did people "boo" XMLHTTPRequest? Because it actually revolutionized the web, and people cheered it.
And yet, they didn't cheer ActiveX. For some reason you assume that every single API Google pushes out is XHR, and not ActiveX
>every view that is not praising Google's take over of the web is skewed
I am not praising Google. I'm simply pointing out that Apple is using abusive business tactics to prevent any competition. It's antitrust territory, and the DOJ agrees. I don't care which browser implements the APIs I need to access, so long as one of them does.
>No. Not on the web they can't. Once it's shipped, people depend on the functionality. That is why we're stuck with so many crappy unfixable APIs in the platform.
Just more skewed nonsense. This can and have been fixed on the web. I've had to reimplement countless APIs for all kinds of services. There are new APIs that make old ones deprecated all the time. Maybe you should try to keep up instead of stagnate like Apple is.
>And yet, they didn't cheer ActiveX. For some reason you assume that every single API Google pushes out is XHR, and not ActiveX
Just more bullshit from you. I'm tired of it. You aren't even attempting good faith arguments.
> I'm sorry, but that doesn't seem to be right. They have a process:
Yes, they do. It's their process, and their timelines. Many features on the page we're discussing are literally "drew on a napkin, not part of any standards process at all, shipped in Chrome"
That's not exactly how standards work. A browser (or anyone) comes up with a spec, a browser can ship it (to test the waters in an origin-trial, to gain traction if they believe in it), and the standard (often) comes after the fact:
"Working Groups don't gate what browsers ship, nor do they define what's useful or worthy. [...] In practice, they are thoughtful historians of recent design expeditions, critiquing, tweaking, then spreading the good news of proposals that already work through Web Standards ratified years after features first ship, serving to licence designs liberally to increase their spread."
https://infrequently.org/2025/09/standards-and-the-fall-of-i...