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

Re: [csswg-drafts] [css-scoping] Support for CSS namespaces (#270)

From: Slawomir Brzezinski via GitHub <sysbot+gh@w3.org>
Date: Mon, 25 Nov 2019 01:31:28 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-557953707-1574645486-sysbot+gh@w3.org>
3 years passed, but still no promised wiki where community could be helped to waste less time yet*). But on a relevant note, there's now [yet another github thread](https://github.com/w3c/csswg-drafts/issues/3547#issuecomment-524206816).

Interestingly, it's main suggestion [brought an idea](https://github.com/w3c/csswg-drafts/issues/3547#issuecomment-521019140) that seems very much like [the `@scope` spec](https://www.w3.org/TR/2014/WD-css-scoping-1-20140403/#scope-atrule) dropped from the CSS**).

More interestingly, [it's current latest suggestion](https://github.com/w3c/csswg-drafts/issues/3547#issuecomment-524206816) allows to add a lower boundary to the @scope rule, which seems interesting.

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 clause
@scope .post {
  p { border-top: red }


_*) As [said before](https://github.com/w3c/csswg-drafts/issues/270#issuecomment-364798933), it would help to curate an unduplicated list of all of the good and bad consequences of the said feature can, and it would be easy to discover existent points already made, and every attempt at adding to the list is welcome..._

_**) About which I learned in the hereby thread, in [this comment](https://github.com/w3c/csswg-drafts/issues/270#issuecomment-234002908)). BTW: I seem to agree with @fantasai on this one - that proposal seems equivalent to this namespaces proposal if namespaces were represented by special class names, but that one seems to be even more powerful, as it leaves more freedom to the users in that it doesn't necessarily require the HTML content to change - the effect can be applied through selectors with a semantic approach_

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

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