Yes, you post this every time as if that absolves Chrome, or you, of shipping "standards" against objections from both Mozilla and Apple, or before consensus on APIs and capabilities, or before even having a spec that others can implement.
To quote your article: "every vendor always ships "whatever it wants."
Indeed, and Chrome ships constantly, recklessly and with hardly a lip service to the standards process.
Your article does have its funny moments. "Blink's rigorous launch process frequently prevents unvalidated designs from shipping". Lol. Lmao even.
You, more than most other people, should know that once something is shipped, it stays in the platform forever, and it's very hard to change something that is already shipped. Yet not only Chrome ships features all the time, its team gleefully announced those features as fait accompli standards on web.dev, and then developers including you demand that other browsers implement these features.
troupo|4 months ago
To quote your article: "every vendor always ships "whatever it wants."
Indeed, and Chrome ships constantly, recklessly and with hardly a lip service to the standards process.
Your article does have its funny moments. "Blink's rigorous launch process frequently prevents unvalidated designs from shipping". Lol. Lmao even.
You, more than most other people, should know that once something is shipped, it stays in the platform forever, and it's very hard to change something that is already shipped. Yet not only Chrome ships features all the time, its team gleefully announced those features as fait accompli standards on web.dev, and then developers including you demand that other browsers implement these features.
slightlyoff|4 months ago
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?