- From: Rune Lillesveen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Aug 2024 13:17:42 +0000
- To: public-css-archive@w3.org
I am trying to write up a PR for the spec change, but not entirely sure how to express the pseudo element case. We cannot keep the "ultimately originating element" as the starting candidate as that would make us incorrectly skip flat tree ancestors for `::slotted()` and `::part()`. But I think we should keep starting from the originating element for `::first-line` and `::first-letter`, and not consider any in-between containers if the originating element is not the inner-most container. I was thinking about keeping the current wording for pseudo elements which are not [part-like pseudo-elements](https://drafts.csswg.org/css-pseudo-4/#part-like-pseudo-elements), but what about pseudo elements for UA controls like which represent `::file-selector-button`? We should not expose any non-named containers inside that implementation if it uses a UA shadow DOM? Perhaps it works with just explicitly call out `::slotted()` and `::part()` and change "ultimately originating element" to "originating element" for the other cases? -- GitHub Notification of comment by lilles Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5984#issuecomment-2269058091 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 August 2024 13:17:42 UTC