So, web components • break a11y • break progressive enhancement (no SSR, broken without JS) • don't work with SVG • share a global namespace instead of being modular • ... Imagine how much tedious moralising we'd see if JS frameworks shipped with similar limitationshttps://twitter.com/sarahmei/status/1198069119897047041 …
-
-
There are good ideas in the Web Components concepts, and people need to figure out what of the patterns are usable enough for real world (including the accessibility from the beginning). Also: how do Web Components work with NoScript type JS blockers?
-
Re: noscript, it depends on how the elements have been authored. In the markup-is-king approach, the HTML API is in the foreground, slotting is used extensively, and all or nearly all properties are attribute reflections. —
- 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.
