- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Sep 2022 21:43:26 +0000
- To: public-css-archive@w3.org
mirisuzanne has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-cascade-6] Can we replace the selector scoping notation with a new parameter in `querySelector()`? == CSS Cascade L6 defines a [selector scoping notation](https://drafts.csswg.org/css-cascade-6/#selector-scoping) which is functionally the same as the `@scope` rules, but is designed as a selector syntax rather than an at-rule. There is also an inline issue, noting the purpose of that: > This notation was added in order to allow scoping limits to be applied within `querySelector()`. Is this something we want to have? In practice, the selector notation is much more difficult to design in a readable way. The basic syntax is less clear than the at-rule, we haven't yet determined how it interacts with nesting, and it's become a blocker for otherwise-straight-forward issues like #6577. If we don't absolutely need this syntax, and can find another solution for scoping `querySelector()`, I would like to remove it from the spec. My proposal would be: - Add a second `lowerBoundary` parameter to both `querySelector()` and `querySelectorAll()`. - Remove the 'selector scoping notation' from Cascade 6 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7709 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 September 2022 21:43:27 UTC