Mozilla didn't ship a Web Components v1 impl until late '18:https://hacks.mozilla.org/2018/11/the-power-of-web-components/ …
-
-
Replying to @slightlylate @erikcorry and
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 …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @erikcorry and
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/
1 reply 0 retweets 0 likes -
Replying to @slightlylate @erikcorry and
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/
1 reply 0 retweets 3 likes -
Replying to @slightlylate @erikcorry and
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.
1 reply 0 retweets 0 likes -
Replying to @slightlylate @erikcorry and
Moving big sites like YouTube over to V1 -- particularly after Mozilla sunk HTML Imports without a proposed replacement -- has taken time, but is also in-progress.
2 replies 0 retweets 0 likes -
This all sounds great in a consequentialist, "my way was best no matter the means to the end" way (I'm on the chromium train of course). The question up-thread was whether a flag hid V0. Sounds like no, or it wouldn't be used heavily by Google properties. That seems news to Erik.
2 replies 0 retweets 1 like -
This was all pre-Origin Trials (which we'd clearly use now), and comes with big speculative error bars attached about what *could* have happened otherwise. My analysis in '14 was that we'd tried to work with others for ~3 years and were getting no real engagement.
1 reply 0 retweets 1 like -
Replying to @slightlylate @BrendanEich and
...and so the choice was to pine for others to join us (which there was low-to-nil prospect of) or to ship something (which had been behind a flag in varous forms since '11) and see if we could drum up interest by making it "real".
1 reply 0 retweets 1 like -
Replying to @slightlylate @BrendanEich and
I took the explicit gamble of second-mover disadvantage costing us over the long haul (and how it has!), but my perspective is that it worked. Remember, this is the same era that team & I were working to upgrade the rest of our semantics (classes, async/await, css vars, etc.)
2 replies 0 retweets 0 likes
If we had it to do over again, we'd use Origin Trials to iterate for as long as we could -- e.g. the way Web XR has -- rather than doing what we did with WC V0 and Mozilla did with WebVR.
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.