W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-nesting] request to pick up the css-nesting proposal

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Thu, 07 Jun 2018 17:57:41 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-395510350-1528394260-sysbot+gh@w3.org>
> It's clear to me that people don't like repeating selectors, but it's less clear to me whether the desire for nesting is related to manipulating the cascade as well (which is poorly done via nesting, and better done via scoping) or the current specificity effects are exactly what's desired and only a syntactic manipulation is wanted.

I think a lot of chatter has led us to the conclusion that people mostly don't like specificity much in the first place, so adding *more* specificity confusion probably isn't good here. ^_^

More importantly, Nesting is *so useful* as a simple syntactic device that it'll get used solely for readability/maintainability reasons, and layering extra specificity behavior on top of it would cause confusion, I think.

(Plus, as described this isn't Scoping-equivalent anyway. Scoping had a particular element it was scoped to, so it could accurately guard against other scoped rules coming from higher in the tree, and yield to scoped rules coming from lower in the tree.  Just attaching scoping-ish behavior to an arbitrary selector doesn't give the same easy mental model.)

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2701#issuecomment-395510350 using your GitHub account
Received on Thursday, 7 June 2018 17:57:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 September 2019 01:18:58 UTC