- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Feb 2023 14:33:59 +0000
- To: public-css-archive@w3.org
> [#](https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-959733391) I think the proposed "scoped descendant" combinator has an obvious answer - it has to be weak (less than specificity) or else it'll be _incredibly_ confusing. Yes. The story so far has always been that combinators don’t influence specificity, and I think it should be kept that way. The "scoped descendant" combinator should have no influence on it. > [#](https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1407017151) Various people have explored this, and we've consistently come to the same conclusions. Can we either get a counter-example to discuss, or resolve on the direction that has vastly more support, so that this feature can move forward? A reason might be https://github.com/w3c/csswg-drafts/issues/8500#issuecomment-1448243790. I think the outcome of that issue and this issue are tied together. -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1448290505 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 February 2023 14:34:00 UTC