- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Feb 2023 21:15:05 +0000
- To: public-css-archive@w3.org
The alternative to all of that is: we don't need _strict de-sugaring_ - just clarification that proximity is determined: - as a single number determined by the final 'step' (scope or combinator) - for the purpose of that measurement, the 'proximity source' of a combinator (the element to measure against) has to be matched explicitly by the preceding selector-fragment With normal `@scope` rules, we can expect the 'proximity source' to be the `:scope`, but in this case we would be saying that the scoping combinators update the proximity source, without updating the `:scope`. Beyond that, there's no reason to de-sugar fully. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8380#issuecomment-1435275539 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 February 2023 21:15:07 UTC