Re: [csswg-drafts] [css-scoping] Support for CSS namespaces

Scoped styles only protected against leaks in one direction (prevented
 the styles from escaping to the rest of the page). That's nice, but 
the other direction (preventing the rest of the page from accidentally
 styling the component) is also vitally important for the use-case of 
"a composable component that Just Works no matter where I put it in 
the page".  That's what web components are giving us right now.  Cases
 that only need the single-direction protection seem to be much rarer.

You cannot easily mod scoped styles into doing both types of 
protection without getting into most of the complexity of web 
components, so it doesn't seem worthwhile to duplicate effort.  
There's obviously an unfilled niche of *declarative* web components 
when you only need some of the simpler parts of the tech, like style 
boundaries, that currently isn't being filled, but "scoped styles" are
 **not** the way to do that, nor is this spec the right place to 
explore these things.  The correct thing to do is wait for web 
components to settle down a bit and become well-implemented, so we can
 figure out what the best way to extend them to address our use-cases 
is.

Regardless, implementations have explicitly stated that they're not 
implementing scoped styles, and their reasoning applies equally to 
anything adjacent to scoped styles.  We already resolved on this in a 
previous meeting, and there's no indication that attitudes have 
changed in the intervening weeks, so further discussion won't change 
anything.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/270#issuecomment-231901954 
using your GitHub account

Received on Tuesday, 12 July 2016 00:07:36 UTC