Re: [csswg-drafts] [css-shadow-parts] need definition of which pseudo-classes can follow :part() that is sufficient to produce interoperability (#10787)

> I made this list by looking over https://drafts.csswg.org/indexes/#selectors which gets selectors from across the spec landscape, so should be pretty complete (anything it's missing are just mis-tagged).

I checked the list in the index against Chrome's implementation.  The only pseudo-elements and pseudo-classes I found that aren't in the list, aren't prefixed, and don't work only on something else that's prefixed (like `::-webkit-scrollbar`) are:
* `:window-inactive` (shipping)
* [`:xr-overlay`](https://www.w3.org/TR/webxr-dom-overlays-1/#css-pseudo-class) (shipping)
* [`:granted`](https://github.com/WICG/PEPC/blob/main/explainer.md) (not enabled yet)
* [`::search-text`](https://github.com/w3c/csswg-drafts/issues/3812) (not enabled yet, not sure of status)
* [`::column`](https://github.com/flackr/carousel/blob/main/fragmentation/README.md),  [`::scroll-next-button`, and `::scroll-previous-button`](https://github.com/flackr/carousel/tree/main/scroll-button) (early carousel experiments, not enabled yet)

I don't think there are any mistagged specs in the CSS WG for any of these, though maybe `:xr-overlay` should show up in the index.

-- 
GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10787#issuecomment-2366954116 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Sunday, 22 September 2024 20:39:31 UTC