> A lot of what happens in someone like Chrome implements something not yet standardized, then it gets standardized in a different way This. The Chrome team is

> A lot of what happens in someone like Chrome implements something not yet standardized, then it gets standardized in a different way This. The Chrome team is hopelessly optimistic when making assumptions about how standards evolve. See Web Bluetooth which was heavily advertised to developers before other browser eventually chimed in and said, "yeah, we're not doing that." Still turned on by default in modern Chrome without a flag, probably because the Chrome team is still assuming that eventually the API will be standardized to Chrome's specification.