Both Firefox and Safari consider them harmful in their current state and will not implement them.
They have not been declared standards by any standards body.
And yet, Chrome goes through a superficial standards-track-like process:
- implements them behind a feature flag
- publishes a draft of the standard
- asks other browser vendors for their position on "emerging standard". Example, https://github.com/mozilla/standards-positions/issues/459
- ignores feedback, and enables by default (see link above)
- advertises as fait accompli (example, https://web.dev/hid-examples/)
- includes these APIs in standard web API counts https://web-confluence.appspot.com/#!/confluence
- proceeds to gaslight other browser vendors as being too slow, holding back the web, holding back innovation etc. through dozens of talking heads with outsized influence (Alex Russel, Justin Fagnani, ... to many to list)
