There is no truer litmus test of a web developer's understanding of mobile vs. desktop in 2018 than their opinion of Web Components readiness. Desktop devs over-index on IE/Edge while mobile (future) oriented folks are like "yeah, of course they're available".
-
-
The biggest problem with using Web components for us is the old WebView on Android 4-5 that still has significant market share

-
This is surprising! The polyfills should work. I also see < 10% share for non-auto-updating webviews. Are these non-Play devices?https://developer.android.com/about/dashboards/ …
- 2 more replies
New conversation -
-
-
I am advocating for a top level script: <script>if(!this.customElements)document.write('<script src="document-register-element.js"><\x2fscript>')</script> which: ∙ would never affect browsers that already ship Custom Elements ∙ would just work in ancient browsers + IE/Edge

-
From my experience Custom Elements alone without Shadow DOM (I refer specifically to slots here) are quite hard when it comes to components that are more complex than buttons.
- 2 more replies
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.