- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Fri, 14 Nov 2025 07:37:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `break`. <details><summary>The full IRC log of that discussion</summary> <astearns> topic: break<br> <kbabbitt> scribenick: kbabbitt<br> <kbabbitt> github: https://github.com/w3c/csswg-drafts/issues/12158<br> <kbabbitt> sakhapov: coming back to CSSPseudoELement object<br> <kbabbitt> ... it's a proxy for an element<br> <kbabbitt> ... but element can exist or not exist<br> <kbabbitt> ... and what it means depends on what we discussed<br> <kbabbitt> ... for :after it can mean rendered, for :selection it can mean something's selected<br> <kbabbitt> ... sometimes we need to know if the thing exists<br> <kbabbitt> ... 2 approaches suggested: synchronous exists property<br> <kbabbitt> ... second suggestion by noam, pseudo element observer<br> <kbabbitt> ... which is a synchronous way<br> <ntim> q+<br> <kbabbitt> ... tells you which were added and which were removed<br> <astearns> ack florian<br> <kbabbitt> ... can use this to add event listeners<br> <kbabbitt> ... most use cases I can think of right now are covered by observer<br> <kbabbitt> ... for example if you think about scroll markers, you might want stats on which scroll marker has been clicked<br> <kbabbitt> ... observer is better for this case becaues it tells you scroll marker has been created<br> <kbabbitt> ... I also think there are possible use cases for sync .exists property<br> <kbabbitt> ... which I listed in 2nd to last comment in issue<br> <kbabbitt> ... first is, might want another event listener which checks existense of pseudo<br> <kbabbitt> ... might want sync approach<br> <kbabbitt> ... also, point is that observer probably is not suitable for non tree abiding pseudos<br> <kbabbitt> ... those are more like states than nodes<br> <kbabbitt> ... also some libraries if you use them might want to init first with knowledge of sync existence of pseudos<br> <kbabbitt> ... those use cases for now are more theoretical<br> <kbabbitt> ... but I think they can be things we might need in the future<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12158#issuecomment-3531338437 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 14 November 2025 07:37:10 UTC