[slightlyoff]

Let's try this again: was Apple wrong to ship Storage Access ahead of everyone else?

https://caniuse.com/mdn-api_document_requeststorageaccess

In the world you want, how should leadership in designs manifest when there isn't consensus? Should nothing ship? And who does that help?

[troupo]

Let's try this again:

Chrome ships dozens of APIs that it then advertises as fait accompli standards. Often when there's even no consensus on the shape of an API. Or worse (see WebHID which Chrome shipped literally without an actionable spec).

Did Safari ship requestStorageAccess in the same manner? If yes, yes it was wrong. It's not a trick question though you somehow think it is.

Again, and it's insane that I have to explain it to you, of all people: once something is shipped in the browser, it stays there forever because people end up using and depending on that feature. And for the past decade that is exponentially "whatever Chrome ships".

It's funny how you lament that Safari is somehow sabotaging standards processes when your former employer literally shits on the whole standards processes and just ships whatever it desires. Oh wait, in your mind it's good because "Blink has a rigorous process" (aka ship whatever our internal company turf wars need right now) and "Blink is a democratic process" (aka whatever Google decides ends up in the browser).

> In the world you want, how should leadership in designs manifest when there isn't consensus?

Ah yes. "Leadership". Justin Fangnani said it was "courage" when they shipped Constructible Stylesheets with no consensus on APIs and a trivially reproducible race condition in the spec just because Google-developed lit needed it. And then tried to gaslight everyone who didn't agree.

It's not leadership. It's a monopoly (or near-monopoly) browser doing whatever the hell it wants with utter disregard to anything or anyone.

Edit

> Should nothing ship? And who does that help?

Literally everyone. Many, many, many people have pointed it out on many occasions that just adding hundreds of new APIs per year to the platform doesn't much benefit the platform. Often you end up with badly designed badly specced APIs that need dozens of workarounds to fix while making the platform itself incomprehensibly complex.

Quirks Blog said it better than me: https://www.quirksmode.org/blog/archives/2015/07/stop_pushin... and https://www.quirksmode.org/blog/archives/2021/08/breaking_th...

In your world "leadership" somehow means "ship whatever whenever at neck breaking pace ä, who cares about consequences".

To quote Steve Jobs (whom you probably hate): "It means saying no to the hundred other good ideas that there are. You have to pick carefully... Innovation is saying no to 1,000 things.".

Chrome's mottos seems to be "we don't take no for an answer, ship it"

[slightlyoff]

It's not insane that you have to explain it to me, because your premise is _wrong_. Go look at the founding documents for web SDOs. Voluntary adoption is foundational to the entire effort, and as I keep pointing out, Apple is the only party that has undermined it:

https://infrequently.org/2025/09/apples-crimes-against-the-i...