Indeed they haven't. They are, at most, drafts or even "draft community reports". And yet, Chrome goes through a superficial standards-track-like process: - i

Indeed they haven't. They are, at most, drafts or even "draft community reports". 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 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/ https://web.dev/hid-examples/) - includes these APIs in standard web API counts https://web-confluence.appspot.com/#!/confluence 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)