- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Jun 2021 16:56:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Remove the :scope dependency from the relative selectors definition`. <details><summary>The full IRC log of that discussion</summary> <Rossen_> topic: Remove the :scope dependency from the relative selectors definition<br> <Rossen_> github: https://github.com/w3c/csswg-drafts/issues/6399<br> <TabAtkins> bkardell_: Selectors spec has :has(); we introduced a :scope pseudo alongside it. In qSA() it's very useful, but it's basically equivalent to :root in normal stylesheets.<br> <TabAtkins> bkardell_: Now :has() allows "relative selectors", starting with a combinator.<br> <TabAtkins> bkardell_: And :scope refers to that implicit starting element, and can be used later in the selector.<br> <TabAtkins> bkardell_: This causes a lot of issues; we'd prefer to drop the relative selector, and make the implicit starting element not be matched by :scope<br> <TabAtkins> bkardell_: I think current prior impl for it is only Prince. They do seem to support it.<br> <TabAtkins> bkardell_: But this is just a lot more difficult in the live profile<br> <TabAtkins> bkardell_: Issue goes into a lot more detail, looking for thoughts and feedback.<br> <TabAtkins> oriol: In most cases, when there's a selector inside of :has() that has :scope, you can refactor it to move that reference outside of the :has() and not lose any functionality<br> <leaverou_> +1 to whatever restrictions we need to place on :scope to make :has() happen<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6399#issuecomment-871573753 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 June 2021 16:56:55 UTC