Re: [csswg-drafts] How to handle addEventListener on `CSSPseudoElement`? (#12163)

While I think the more limited proposal where we expose the pseudo-element on the event and you can opt-in to get more events as was floated at the end of the meeting might be more reasonable, it still seems rather worrisome overall.

Say these event listeners open popovers, what is going to be the source? How will this be exposed to AT? How will this interact with the various focus traversal proposals? Having actual elements to represent semantics seems much more structurally sound. And note that it could potentially be one element representing a variety of functionality, such as we have with media elements, depending on the exact use case.

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


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

Received on Friday, 8 August 2025 10:34:35 UTC