Earlier quoted context omitted.
I know people get incredibly upset whenever this gets mentioned because suddenly they DO want it again but that was a big part of what “web components” were. When you need that level of isolation you can get it for free without any extra work.
Web Components are doing much more with isolation than just isolating styles. You don't want/need to kill your a11y, form participation, and a bunch of other things (and laboriously solve them with Javascript) just because you want to scope your styles
Inline Scope for CSS
41–43 of 43 posts
Re: Inline Scope for CSS
#42Earlier quoted context omitted.
Web Components are doing much more with isolation than just isolating styles. You don't want/need to kill your a11y, form participation, and a bunch of other things (and laboriously solve them with Javascript) just because you want to scope your styles
Form participation has been fixed for a while now for the record.
Too much hassle when all you need is style scoping
Re: Inline Scope for CSS
#43For now, as Firefox support is not yet good, We can use nested rules in CSS. HTML: This is a paragraph CSS: my-custom-element { p { color: blue; } } By choosing a unique name for the custom element, we achieve near the same functionality as @scope.
Is this not the same as having a class with a unique name, and applying it to a parent div