- From: Bramus via GitHub <sysbot+gh@w3.org>
- Date: Mon, 27 May 2024 12:30:21 +0000
- To: public-css-archive@w3.org
bramus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-cascade-6] Publish an updated WD == Looking at [the current WD of css-cascade-6](https://www.w3.org/TR/css-cascade-6/) it still includes both the strong and weak scoping steps in the cascade. Since then, with the WG we settled on using only weak scoping, among a few other changes & additions, [as listed in the changes](https://drafts.csswg.org/css-cascade-6/#changes-2022-08): > - Clarified that [scope proximity](https://drafts.csswg.org/css-cascade-6/#scope-proximity) is a single measurement of the steps between a single [scoping root](https://drafts.csswg.org/selectors-4/#scoping-root) and [scoped style rule](https://drafts.csswg.org/css-cascade-6/#scoped-style-rules) [subject](https://drafts.csswg.org/selectors-4/#selector-subject). > - Removed strong scope proximity. ([Issue 6790](https://github.com/w3c/csswg-drafts/issues/6790)) > - Removed the scoped descendant combinator (deferred). ([Issue 8628](https://github.com/w3c/csswg-drafts/issues/8628)) > - Added the [CSSScopeRule](https://drafts.csswg.org/css-cascade-6/#cssscoperule) interface. ([Issue 8626](https://github.com/w3c/csswg-drafts/issues/8626)) I think it would be good to publish an updated WD as authors that read the WD will be confused: the thing that’s shipping in Safari and Chrome (and Firefox in the future) implements the cascade as currently described only in the ED, not the WD. Any concerns with this, @mirisuzanne? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10370 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 27 May 2024 12:30:22 UTC