4 ms·
Chrome likes to make up new "standards" and then some websites adopt them immediately. That said, I can only remember two instances of that slightly inconvenie
by input_sh 5mo ago
Chrome likes to make up new "standards" and then some websites adopt them immediately.
That said, I can only remember two instances of that slightly inconveniencing me in the past, and both times I was inconvenienced by a Google-run website: once upon a time Google Earth refused to work, and once upon a time I couldn't tweak my Google Meet background. Both are no longer the case.
- StilesCrisis 5mo agoCitation needed. I've seen the opposite--unless there's a very specific niche that can't be otherwise solved, there's huge internal resistance to going it alone. The biggest counterexample I can think of: WebUSB was critical to Chromebooks supporting external devices, but I can see why Safari might not want it. It has Firefox support at last, though.
- input_sh 5mo agoCitation of what exactly? That not all browsers implement the same thing at the same time and that some features are Chrome-exclusive because for one reason or another other browsers refuse to implement it? Is that really something you need a citation on? You sure seem to have come up with an example of your own.
- StilesCrisis 5mo ago"Chrome likes to make up new standards" I can think of just one, USB. Chrome was built on the premise that web standards matter. Remember IE 6?
- pamcake 5mo agohttps://www.theregister.com/software/2026/04/30/mozilla-pushes-back-against-googles-prompt-api/5223409 https://www.theregister.com/software/2026/04/30/mozilla-push... Remember AMP?
- StilesCrisis 5mo agoAMP wasn't part of Chrome. The Prompt API is part of a real W3C standard: https://www.w3.org/2025/03/webmachinelearning-charter.html https://www.w3.org/2025/03/webmachinelearning-charter.html It's not even chaired by Google. It's Intel, believe it or not.