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

The CSS Working Group just discussed ``How to handle addEventListener on `CSSPseudoElement`?``.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> sakhapov: so PseudoElement inherits from EventTarget<br>
&lt;TabAtkins> sakhapov: how do we represent this, without webcompat problems<br>
&lt;TabAtkins> sakhapov: proposal is to add pseudoElementTarget and currentPseudoElementTarget, similar to target and currentTarget. Will have to discuss this with DOM folks as well, but wanted opinions here first<br>
&lt;TabAtkins> flackr: sounds good<br>
&lt;TabAtkins> Yeah, I think this is what we need, can't set .target to a PseudoElement without breaking code<br>
&lt;TabAtkins> sakhapov: anne pointed out it might be a layering violation<br>
&lt;TabAtkins> flackr: i think the point is just that the html spec needs to call into the css pseudo spec to set up this property on the event<br>
&lt;TabAtkins> sakhapov: okay, if no one objects i'll propose this at the WHATNOT html meeting<br>
&lt;TabAtkins> fantasai: Anne says he wants more time to consider flackr's idea, also wants to hear from smaug from Moz since he's been involved with events for a long time<br>
&lt;TabAtkins> astearns: i think taking this to HTML is the right next step, to get feedback there as well<br>
&lt;TabAtkins> astearns: we ahve a joint meeting with whatwg every other thursday<br>
&lt;TabAtkins> sakhapov: sounds good<br>
</details>


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


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

Received on Wednesday, 25 June 2025 15:54:23 UTC