I heard they always use flags to prevent forging de facto standards. Not in CE’s case?
-
-
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 -
Replying to @ManishEarth @slightlylate and
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.
1 reply 0 retweets 3 likes -
That's exactly the problem you get, as night follows day, with one implementation shipping unflagged.
1 reply 0 retweets 3 likes
-
-
Replying to @slightlylate @BrendanEich and
It is *insane* to me that other vendors don't have this infrastructure yet. It keeps us from shipping bad things all the time, and gives us *so* much more space to iterate.
2 replies 0 retweets 2 likes -
Replying to @slightlylate @BrendanEich and
Things like U2F and WC v0 are water under the bridge. How we do better from here is what matters.
1 reply 0 retweets 2 likes - 1 more reply
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.