Ultimately, it's a fine line and I think as long as the folks are creating solutions, getting feedback and ensuring that they're building something people want to use - then I say carry on. IF that isn't happening then we're just creating bloat not only to the binaries but...
We built (and shipped, and then unshipped) `<style scoped>` which was ~roughly this:
https://developers.google.com/web/updates/2012/03/A-New-Experimental-Feature-style-scoped …
@tabatkins will likely remember more about why we abandoned, but perf impact was unacceptable IIRC.
-
-
Is it equivalent? It feels very different — less composable, results in more duplication
-
The idea of a syntax for opting a rule-set (or set of rule-sets) into a particular group was also explored. Same perf implications at style resolution time.
- 4 more replies
New conversation -
-
-
There may have been perf implications, I don't recall. My reason for abandoning it was that upper-boundary (prevent styles from escaping) without lower-boundary (prevent styles from infecting) protection ended up of minimal use in practice to our early devs. Mostly a footgun.
-
@stubbornella had been doing great work collecting and synthesizing use-cases and problems that drive people to various solutions, and has identified some good remaining functionality holes that I think can be solved pretty easily. - 16 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.