[candiddevmike]

Still sucks to add it to your app. You pretty much have to use a library or you'll be maintaining all of the device level quirks yourself. OIDC has the same problem where the standard was too loosey goosey and didn't provide a true standard interface, leading to some special handlings for providers.

IMO, folks who write standards need to write them with the best interests of the developers who will be integrating it, not the service providers.

[AmericanChopper]

Nice idea but I’m not sure it would matter. Nobody implements standards, even when they’re properly defined.

[lll-o-lll]

They do when there is a certification process. That’s the key to a well defined standard, a certification. The test suite is the real standard.

[AmericanChopper]

My personal experience with certified implementations is that they still tend to be not especially standardised. A test suite is just as susceptible to subversion as a written standard is. If that wasn’t true then unit tests is all we’d ever need to merge a PR.

[RussianCow]

Businesses still need their stuff to work on Chrome whether or not it's certified, so this is kind of a moot point.