The important point here is that what the web needs is a set of browsers/engines competing *at the leading edge*. Multi-year delays in delivering features to 90+% of users are all-too common, and the problem isn't update rates any more.https://twitter.com/jyasskin/status/1207739254480048128 …
-
Show this thread
-
Alex Russell Retweeted Marcos Càceres
E.g.: https://twitter.com/marcosc/status/1207512288938192896?s=20 … Consider: 1.) Moz killed WCv0 & knifed imports in Q4'14 2.) All (Google, Apple, MSFT, Mozilla) agreed WCv1 by Q4'15 3.) Chrome shipped v1 in Q4'16, Safari in Q1'17 4.) Mozilla didn't ship until *Q4'18* 5.) Edge finally getting WC w/ Anaheim launch
Alex Russell added,
4 replies 0 retweets 7 likesShow this thread -
-
Replying to @marcosc
Sorry? There's one principled divergence (`is` attr). Everything else works. You simply can't equate that with Mozilla's multi-year delay to ship *anything*.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
X extends HTMLElement doesn’t work
But again it’s a false equivalence: platform featurism isn’t what drives Mozilla.
It’s disingenuous to say Mozilla needs to catch up when we would never ship many of the proposed APIs or features. We are very selective about what we ship.1 reply 0 retweets 0 likes -
-
-
Replying to @marcosc
The heck are you talking about?pic.twitter.com/Mrk3IAsepB
2 replies 0 retweets 2 likes
I mean, per spec, you *do* need to define a real class and call `super()` first in your constructor function, so your *specific* pseudocode there wouldn't work. But this will: ``` class X extends HTMLELement { constructor() { super(); ... } } customElements.define("x-x", X); ```
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.