Today I learned that the way the Google FIDO u2f polyfill is written means the API defined at https://fidoalliance.org/specs/fido-u2f-v1.0-nfc-bt-amendment-20150514/fido-u2f-javascript-api.html#high-level-javascript-api … can't actually be shipped in non-Chrome browsers in that form because the polyfill will stomp on it with code that only works in Chrome.
-
Show this thread
-
I've figured out a way to express in IDL an API that works around what the polyfill is doing, but it involves legacycaller and [LenientSetter] and all sorts of other shenanigans. :(
2 replies 0 retweets 6 likesShow this thread -
Replying to @really_bz @bz_moz
Surely Google wouldn’t engage in this sort of vendor lock in tomfoolery on their own websites.
1 reply 0 retweets 0 likes
Replying to @othermaciej
Sarcasm? ;) In any case, the polyfill in question is widely deployed on non-Google sites too...
10:40 AM - 23 May 2019
0 replies
0 retweets
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.