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 …
This is the specific difference I alluded to re: `is`: https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-customized-builtin-example … Everything else works.
-
-
Is Apple wrong here? Yes. Hopefully the community they've made things difficult for will eventually prevail. Is this a reason not to work on other meaningful things that can improve lives for developers & end-users until then? Heavens, no!
-
...and about those polyfills. The costs associated with Apple being bad/wrong here are: 1.) scoped to only impact the wealthiest users (finally, a non-regressive JS tax!) 2.) *tiny* compared to a full compliment of CE polyfills:https://github.com/WebReflection/built-in-element/#built-in-element …
- 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.
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.