Re: [csswg-drafts] [css-cascade-6] Strong vs weak scoping proximity (#6790)

@matthewp I think the key here is @scope makes this possible now without the framework. I don't think it gives anything new to frameworks, but rather accomplishes something natively that developers have relied on frameworks/CSS-in-JS libs for.

If the author gives each component a unique name/classname, they can manage scoping with native CSS and no ugly BEM class name patterns. With appropriate scoping, developers can style `.card .title` differently than `.callout .title` and not worry about the two `.title` selectors conflicting.

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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 16 March 2023 15:25:34 UTC