3 ms·
I disagree. Chrome, by virtue of its popularity, market power and technical prowess, pushes through new features. In addition to that, they also port features f
by 8ytecoder 6y ago
I disagree. Chrome, by virtue of its popularity, market power and technical prowess, pushes through new features. In addition to that, they also port features from ChromeOS. Most of these features are either not standard yet or would never be.
For example, the WebUSB APIs are still in draft community status but is already there in chrome. Presumably because they created it for chromeos, ported it to chrome and then submitted it to the standards body - in that order. They are definitely going to continue this. I don’t see chrome publishing and getting a standard approved before implementing it at all. It’s also how IE6 holdover came about.
Web developers aren’t supposed to rely on non-standard features because it’s tight coupling and will bite you if the browser ever stagnates. That’s the lesson I learnt from the whole IE6 saga.
https://en.wikipedia.org/wiki/WebUSB https://en.wikipedia.org/wiki/WebUSB
- GekkePrutser 6y agoYeah and Firefox still lacks full passwordless fido2 (ctap mode)
- gfodor 6y agoWell, yeah, you shouldn’t make your site incompatible with browsers that don’t support non-specced features if you can avoid it. Which is what I said the lesson was. But I like WebGL2 and SharedArrayBuffer and don’t feel bad blocking users until their browser catches up.