- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 16:45:36 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-pseudo-4] Semantics of CSSPseudoElement : EventTarget`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-pseudo-4] Semantics of CSSPseudoElement : EventTarget<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4398<br> <florian> s/Sep issue for number/Sep issue for type of number/<br> <dael> fantasai: I don't know what to do with it. I'm asking for help from WG<br> <dael> astearns: Anyone want to jump it?<br> <dael> astearns: Might be better to tag particular people<br> <dael> fantasai: Don't know who<br> <dael> florian: Punt while we figure out event handling for highlight APIs? Might influence here<br> <dael> florian: Until that's resolved we leave this hanging. Unless someone has better idea<br> <dael> sanketj: I think we discussed similar on a different call. I don't think there's impl interest in this area<br> <dael> dbaron: My reaction to the issue is probably worth going slow. One suggestion is this is only for animation events and that might be reasonable way to start<br> <dael> dbaron: Not a good idea to make intent to change event handling in non-backwards compat ways. Difference in how click events are handled is prob not what we want<br> <dael> florian: Even handling on pseudos we haven't attacked precisely, but want to handle it generally. I agree<br> <dael> astearns: Let's leave it here. We have highlight issue linked. This will go into issue<br> <dael> astearns: As dbaron says we can go slowly on this.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4398#issuecomment-805984428 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 March 2021 16:45:38 UTC