- From: Psychpsyo (Cameron) via GitHub <noreply@w3.org>
- Date: Tue, 09 Sep 2025 15:11:20 +0000
- To: public-css-archive@w3.org
Psychpsyo has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-view-transitions-1][selectors-4] Be more specific about what combinators are allowed with view transition pseudo-elements == [Selectors 4](https://www.w3.org/TR/selectors-4/#sub-pseudo-elements) says that sub-pseudo-elements (those whose originating element is another pseudo-element) can be selected by chaining them onto their originating elements. It gives `::before::marker` and `::after::marker` as examples. [View Transitions 1](https://www.w3.org/TR/css-view-transitions-1/#view-transition-pseudos) defines a bunch of sub-pseudo-elements, but then says says that "all of [them] are selected from their [ultimate originating element](https://www.w3.org/TR/selectors-4/#ultimate-originating-element), the [document element](https://dom.spec.whatwg.org/#document-element)". But it never outright says that the regular way of selecting sub-pseudo-elements doesn't apply to them. It should probably do that if that is the intention. (Which, given that the Chrome implementation disallows this, seems likely) Furthermore, [Selectors 4](https://www.w3.org/TR/selectors-4/#pseudo-element-structure) defines pseudo-elements with internal structure and says that these can be selected using `>`. [View Transitions 1] creates a tree of pseudo-elements and calls it "a structure of pseudo-elements" in a note. It is unclear whether this passes as "internal structure" for the purposes of Selectors 4, so clarification in either spec would we welcome. Going off of the Chrome implementation once again makes it seem like this is not meant to be an internal structure. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12757 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 September 2025 15:11:21 UTC