W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2019

Re: [csswg-drafts] [css-scoping] Please bring back scoped styles (#3547)

From: Slawomir Brzezinski via GitHub <sysbot+gh@w3.org>
Date: Mon, 25 Nov 2019 01:56:11 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-557957430-1574646969-sysbot+gh@w3.org>
A bit daunted to see yet another thread on this, despite [the working group setting some expectations that they will help prevent this](https://github.com/w3c/csswg-drafts/issues/270#issuecomment-399671975)...

Trying not to just rant though, I can say though that this thread's proposal is better that that old one (even if part of it look like the historical [`@scope` proposal](https://www.w3.org/TR/2014/WD-css-scoping-1-20140403/#scope-atrule)).

 
Still, as [said previously](https://github.com/w3c/csswg-drafts/issues/270#issuecomment-364677643), I would really like the working group to consider ways of adding scope to the rules outside of the very stylesheet where these rules live, bur rather somewhere in a parent. This would enhance the ability to quote hypertext content with its full richness.
Also as said, both ways could exist, and it would make the feature maximally powerful. E.g. what if this scope clause:

```HTML
<style>
@scope .post {
  color: blue;
}
<style>
```

also caught all `<style>` references inside the `.post`? It even seems quite natural (for web components, e.g.), but if this is too risky of a default, it could be controlled using an explicit version, e.g `@scope::--also-ensclose-contained-stylesheets` (name deliberately verbose - just for clarity of intent).

-- 
GitHub Notification of comment by zlamma
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3547#issuecomment-557957430 using your GitHub account
Received on Monday, 25 November 2019 01:56:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:56 UTC