- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Aug 2024 17:39:56 +0000
- To: public-css-archive@w3.org
> I think there's also an open question about how to extend the rule that `::part(a)::part(b)` is not allowed to part-like pseudo-elements. I think perhaps the right rule is that part-like pseudo-elements and `::part()` can be combined in a [compound selector](https://drafts.csswg.org/selectors-4/#compound) subject to the constraint that the compound selector has at most one `::part()`. But I'm curious if others think that's the right approach. Actually, I think that suggestion was more complex than needed. I think since pseudo-elements are built-in, and we aren't planning to expose parts on built-in things, there isn't any need for `::part()` following part-like pseudo-elements. So I think probably the rule that we want is that `::part()` is not allowed after `::part()` or any part-like pseudo-element. Then we don't need any constraints about the entire compound selector and can continue to describe the rules in terms of "is X allowed to follow Y". -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10083#issuecomment-2315922234 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 August 2024 17:39:57 UTC