the <toast> element proposal is such a perfect illustration of the incentive structure bred by the internal Google dynamics around the Mobile Webhttps://twitter.com/jensimmons/status/1138980859728531456 …
Mozilla didn't ship a Web Components v1 impl until late '18:https://hacks.mozilla.org/2018/11/the-power-of-web-components/ …
-
-
And legacy Edge never implemented v0 or v1, despite the constituent APIs being the most popular requests for many years: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/filters/top …
-
So mobile browsers got to ~full Web Components coverage in early '18 when UC switched to a modern Chromium. Desktop will pull into port when IE 11 is gone and Chromium-based Edge ships (imminently! hooray!): https://www.microsoftedgeinsider.com/en-us/
- 8 more replies
New conversation -
-
-
Wasn't this in part due to compat issues caused by v0? We had similar problems with U2F -- Firefox got U2F support two years ago but couldn't ship it for quite a while because sites used Google's u2f.js which relied on implementation details.
-
And the end result was that websites would feature-detect u2f, try to use it, and break completely because their u2f wrapper expected Chrome's impl.
- 5 more replies
New conversation -
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.