zlacker

> But the chance of a web page actually needing that functionality to render at all is rare for hopefully-obvious reasons.

The chance of a page using something has no bearing on how dificault something is to implement.

> People get upset about WebUSB... but that's not the API surface that is causing us issues.

It's one of the hundreds of APIs, and yes, it causes issues, too. Because it also needs to be implemented, and it also adds to the complexity of the web browser.

>>troupo+(OP)
No: it doesn't need to be implemented unless you actually want to do something with USB. Random websites aren't not working because you don't support USB. My iPhone doesn't support WebUSB even if I updated its firmware.

>>saurik+9q
> No: it doesn't need to be implemented unless you actually want to do something with USB

Tell it to angry devs even here who lambast Safari and Firefox for not implementing Chrome's hardware APIs