All browsers to support native web components on January 15th! 
https://twitter.com/kylealden/status/1191366576651538434 …
-
-
Replying to @justinfagnani
What about UC browser... 'all' is perhaps a bit overstated.
1 reply 0 retweets 0 likes -
Replying to @alexanderdanilo @justinfagnani
UC moved to Chromium last year, so yes, "all".
1 reply 0 retweets 3 likes -
So, browsers are getting web-components support via switching to a single engine. Don’t you see some flaws in this path?
2 replies 0 retweets 1 like -
WebKit and Gecko implemented independently, backstopped by an expansive test suite we all contribute to. So I challenge the premise.
1 reply 0 retweets 0 likes -
At the same time Presto and EdgeHTML could not keep it up and the total number of engine vendors is shrinking. The trend is very devastating.
2 replies 0 retweets 0 likes -
There's a hierarchy of concerns here. Losing two closed-source engines while retaining the ability for all of those vendors to go their own way (via forks) should this go south seems less bad to me than an even-lower rate of platform improvement.
1 reply 0 retweets 0 likes
Would I prefer all firms to bulk up their engine teams to keep the pace? Absolutely. Should we slow down and fail to compete with native? Not a chance. I weight the latter higher than the former but know that's not a universal view and respect that perspective.
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.