Hacker News new | ask | show | jobs
by input_sh 40 days 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.
1 comments
StilesCrisis 40 days ago
Citation 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.

link
input_sh 39 days ago
Citation 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.

link
StilesCrisis 39 days 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?

link
pamcake 39 days ago
https://www.theregister.com/software/2026/04/30/mozilla-push...

Remember AMP?

link
StilesCrisis 39 days ago
AMP wasn't part of Chrome.

The Prompt API is part of a real W3C standard: https://www.w3.org/2025/03/webmachinelearning-charter.html

It's not even chaired by Google. It's Intel, believe it or not.

link