The proposal does have merit: it probably would be good for screen readers (though <dialog> or aria role=dialog probably suffices? maybe?) but that's not really front-and-center, it's "developers might get this wrong" (which is what libraries are for)
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/
-
-
There are lots of good outcomes from browsers finally agreeing a component model (even if it isn't perfect). For instance, Mozilla is re-doing their entire UI in Web Components: https://briangrinstead.com/blog/
-
And massive organisations like Google and Salesforce are able to move their UIs off of warring stacks onto a common infrastructure. Google's components are currently transitioning (more than 10K of them!) at a rapid pace to v1.
- 6 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.