5 ms·
https://caniuse.com/#search=webauthn https://caniuse.com/#search=webauthn
by tofflos 8y ago
https://caniuse.com/#search=webauthn https://caniuse.com/#search=webauthn
- smacktoward 8y agoThat's... actually not as bad as I was expecting it to be. If you're willing to limit your audience to modern browsers only, the only holdout is Safari; and on that score, what else is new.
- dan1234 8y agoIt’s actually included as an Experimental Feature in the preview version of Safari, so there’s some hope that it will be present in the mainline version before too long.
- ljm 8y agoI got a YubiKey a year or so back and looked at this. It seems like Safari's holding out on a confirmed spec because before then it was a bit too Chrome-specific.
- zanny 8y agoIts not just whether the API is available but whether its practical to use. I'm not sure which browsers recognize or support fingerprint readers, though all the implementations seem to support usb u2f. Feels like a total failure to launch that the spec doesn't recommend the use of browser accounts as credential providers. Every single major browser has an associated web account with it (Firefox Account, Google account, Microsoft account, Apple id, etc) and could trivially use those accounts as authentication providers.
- michaelt 8y agoThat would make it difficult to change browsers, wouldn't it? Or indeed to use different mobile and desktop browsers?
- gsnedders 8y agoIt's unsurprising this is the case: to be published as a Recommendation you have to demonstrate interoperable implementation experience. The implementation report is at https://www.w3.org/2019/01/webauthn-report.html https://www.w3.org/2019/01/webauthn-report.html and shows Safari passing most of it, AFAICT. (Though it's based on Safari Technology Preview and is yet to ship.)
- imtringued 8y agoI don't really get how that is surprising. Soon chrome based browsers will have 80% of the market share and more.