- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 22 Apr 2026 16:14:53 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-pseudo] Add ::backdrop and ::view-transitions to the CSSPseudoElement's allowed pseudo-elements list`, and agreed to the following: * `RESOLVED: use the CSSPseudoElements interface for all standardised tree-abiding pseudo elements` <details><summary>The full IRC log of that discussion</summary> <JoshT> sakhapov: now have the pseudo element JS interface<br> <JoshT> ... biggest useful thing would be events<br> <JoshT> ... click on some pseudo element in the target<br> <JoshT> ... pseudo elements supports before and after. could add ::backdrop and ::view-transitions as well<br> <JoshT> ... example for ::backdrop would be when you have modal open and you want to click outside of window, people currently have to do geometry intersection stuff<br> <JoshT> ... with this, you just check if the click target was the pseudo element<br> <flackr> q+<br> <JoshT> ... for ::v-t, bramus shows if you have an ongoing v-t, you can intercept to start a new one<br> <JoshT> ... for scroll-marker and scroll-buttons, you could target them<br> <JoshT> ... proposal is to follow Rob's suggestion to add all tree abiding elements to pseudo element interface<br> <JoshT> flackr: given that proposal, that sounds good. we know strong use case for the scroll pseudos<br> <bramus> +1 on tree-abiding<br> <JoshT> ... tree abiding elements have well established way of working<br> <emilio> q+<br> <JoshT> astearns: makes sense. am I right that there's no back compat issues or problems from if engines are scattered in their support. they don't need to support all tree abiding pseudos all at once?<br> <JoshT> flackr: you get the event anyway. this is about if the target is a pseudo<br> <JoshT> ... for unsupported, you just have no target but still see the event<br> <JoshT> astearns: so at that point, you don't know if it's lack of support or just whether the event didn't hit the pseudo<br> <astearns> ack emilio<br> <JoshT> flackr: that's the situation today<br> <astearns> ack flackr<br> <JoshT> emilio: did we figure out how in out events behave with pseudos?<br> <JoshT> ... do you get a mouse event?<br> <JoshT> sakhapov: we decided to disable for now<br> <JoshT> flackr: they don't cause boundary events<br> <JoshT> ... you just say this event is targetted to the pseudo<br> <JoshT> emilio: so you cannot observe whether ???<br> <JoshT> ... concern is whether all tree abiding elements doesn't include non standard stuff<br> <JoshT> ... presumably it would include ::-webkit-, which could cause compat problems<br> <JoshT> ... there are some details about layout of other tree abiding elements, but maybe that's ok<br> <JoshT> ... concerned about people building custom effects for inputs that only work on -webkit- pseudos<br> <JoshT> flackr: i'd support adding a condition for only standard pseudos<br> <JoshT> sakhapov: considered adding select, but I will raise a new issue<br> <JoshT> emilio: for pseudos that represent multiple things, it's tricker<br> <JoshT> ... these aren't part of the resolution because they're real elements<br> <JoshT> sakhapov: maybe I can get a specific list of what we have and if no one objects, we can accept<br> <JoshT> astearns: a list instead of the general tree abiding elements solution?<br> <JoshT> sakhapov: maybe not? we can go with the general solution<br> <JoshT> astearns: my preference is the standard tree abiding pseudos with some examples like '::part included because it's an element' etc<br> <JoshT> PROPOSED: use the CSSPseudo interface for all standardised tree-abiding pseudo elements<br> <ChrisL> q+ to check this is for selectors-5, right?<br> <JoshT> ChrisL: this is for selectors-5, not 4, right?<br> <JoshT> sakhapov: this is in pseudo elements 4<br> <JoshT> RESOLVED: use the CSSPseudoElements interface for all standardised tree-abiding pseudo elements<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13804#issuecomment-4297936996 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 April 2026 16:14:54 UTC