Re: [csswg-drafts] [css-pseudo-4] Proxying pseudo-elements as "real" (`<slot>`) elements (#12575)

A few questions:

- I'll cite @flackr from https://github.com/w3c/csswg-drafts/issues/12163#issuecomment-3175171832:
> Not all pseudo-elements are trivially replaced with real elements. There are many use cases where they are dynamically generated, even according to layout as in the carousel use case where you get a ::column::scroll-marker for each page of content which depends on the layout of the box (e.g. [chrome.dev/carousel/horizontal/pages](https://chrome.dev/carousel/horizontal/pages/), [codepen.io/flackr/pen/yLmyPEV](https://codepen.io/flackr/pen/yLmyPEV)). Developers cannot simply provide real elements because they don't know how many or which items are in each column.

Probably fixable by introducing an index to `::column` though. But what if there will be more pseudos like that?
- Will there be a way to understand that the pseudo "exists"? For CSSPseudoElement there is a plan for https://github.com/w3c/csswg-drafts/issues/12158.

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


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

Received on Tuesday, 12 August 2025 10:56:33 UTC