- From: Daniil Sakhapov via GitHub <noreply@w3.org>
- Date: Mon, 11 Aug 2025 19:33:06 +0000
- To: public-css-archive@w3.org
But then once again we'll reach the limitation of real elements not being able to represent the `::column::scroll-marker` and `::view-transition` cases. Do you have any other ideas we can potentially discuss? The latest proposal seems to be quite straightforward to comprehend, safe for the web compat and quite future proof for new pseudos/event types. With one central `CSSPseudoElement` interface to cover all the current and future (like adding geometry utils) author's needs to work with pseudos. I understand the general vibe not to make pseudos more powerful and complicated, but the pseudos themselves are becoming more powerful and it seems that we need to keep up with them? This issue and others related are patching the old design mistakes for pseudos in the best possible way. And with the form control styling spec there are a lot of new pseudos coming - https://www.w3.org/TR/css-forms-1 - those also look like they might benefit from addEventListener support. -- GitHub Notification of comment by danielsakhapov Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12163#issuecomment-3176594679 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 11 August 2025 19:33:06 UTC