No thanks. I'll accept it in my browser when they fix the security implications this raises, and when the Spec is no longer in draft.
What are the security implications this raises that downloading native programs (needed for example to flash my smartphone) doesn't raise?
The spec is still in draft because Apple refuses to let it move forward - because WebUSB, WebBluetooth and other APIs would compete with their app store, where they can make money from purchases made through apps. They prioritize profits over progress.
It has nothing to do with security, as WebUSB has no ability to interact with any device unless the user explicitly allows each and every website that requests access to do so. It's the same security as any other browser API that requests access.
And I'll just fire up a chrome instance which I specifically keep for when my daily driver firefox decides to spazz out and not implement basics in 2026 :'(
The security implications of not having WebUSB are having to install untrustworthy native drivers every time you want to interface with a USB device.