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)
-
Show this thread
-
to think Google pushed super hard on Custom Elements -- to the point of jumping the gun on shipping, ending up with an incompatible shipped version-- to not use it as the primary path for situations like these
1 reply 1 retweet 25 likesShow this thread -
Replying to @ManishEarth
I heard they always use flags to prevent forging de facto standards. Not in CE’s case?
1 reply 0 retweets 1 like -
Replying to @BrendanEich
I'm not sure exactly what happened; but "custom elements v0" got used quite a bit, especially on Google properties. YouTube was using v0 (with a slow polyfill for other browsers) for years after v1 shipped
1 reply 1 retweet 3 likes -
-
Replying to @BrendanEich @ManishEarth
I don’t know the history of custom elements sorry, perhaps
@slightlylate ?1 reply 0 retweets 0 likes -
We shipped v0 Web Components in 2014 after multiple years of attempting to collaborate with basically everyone. Weren't many choices & hadn't yet invented Origin Trials (see blog post from '15: https://infrequently.org/2015/08/doing-science-on-the-web/ …)
2 replies 1 retweet 7 likes -
Replying to @slightlylate @erikcorry and
My personal view (not shared by others) is that V0 shipping precipitated others coming to the table to do V1, which we pursued through '15, culminating in Safari and Chrome shipping V1 impls in '16 (Safari was first to their dev channel, we were first to stable)
2 replies 0 retweets 6 likes -
Replying to @slightlylate @erikcorry and
Mozilla didn't ship a Web Components v1 impl until late '18:https://hacks.mozilla.org/2018/11/the-power-of-web-components/ …
2 replies 0 retweets 0 likes -
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.
2 replies 0 retweets 3 likes
V0 sites universally served polyfills. Those didn't interact with V1 (totally different API surface, by design). Mozilla seemingly just didn't put enough people on the project...IDK why.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
