- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 15:19:44 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``Add a property to the `CSSPseudoElement` IDL interface to determine if a pseudo element "exists"``. <details><summary>The full IRC log of that discussion</summary> <sakhapov> sakhapov<br> <ydaniv> sakhapov: want to discuss pseudo-element interface to use it from JS<br> <ydaniv> ... element.pseudo, if object is valid the the pseudo is used<br> <ydaniv> ... has several props like using identity for event delegation<br> <ydaniv> ... ability to distinguish if element is rendered or exists<br> <ydaniv> ... add property exists per element<br> <oriol> q+<br> <ydaniv> ... si add property per element defined and supported<br> <ydaniv> oriol: not sure if this make sense for some elements<br> <ydaniv> ... whether this interface would be able to work for any element, or just tree-abiding ones<br> <ydaniv> ... not sure whether it's well defined<br> <ydaniv> ... also whether if there's a generated box for this element<br> <ydaniv> ... you only want to check whether it exists or not<br> <ydaniv> ... also has perf concerns, to check if has generated boxes<br> <ydaniv> ... so makes sense to add extra APIs for these<br> <flackr> q+<br> <ydaniv> sakhapov: for now defined only for 4-5 elements<br> <astearns> ack oriol<br> <ydaniv> ... we can later defined for other elements, and having same interface for element and pseudo<br> <ydaniv> ... each opseudo is unique and different, so makes sense to define per element, and later generalize<br> <ydaniv> oriol: so makes sense to define per element if box exists or something different<br> <ydaniv> sakhapov: yes, for example for :column<br> <ydaniv> flackr: I think Daniil covered all my points, part of goal here to define the exists and can be different, like whether selection exists<br> <astearns> ack flackr<br> <ydaniv> ... part of it is defined whether exists, because if has box is different<br> <schenney> q+<br> <ydaniv> sakhapov: gCS for highlight pseudos it returns styles as if active, so not same as box is present<br> <astearns> ack dbaron<br> <ydaniv> dbaron: I think this seems reasonable, agree we define existance per element<br> <ydaniv> ... for customisable select we defined sepcific mechanism, my intuition is that it should return true only if has select on element, .... <missed><br> <TabAtkins> Big +1 to dbaron (and I think I feel a bit more strongly about it)<br> <dbaron> questions: 1. whether ::checkmark existing depends on whether the <select> has appearance:base-select<br> <dbaron> 2. whether ::checkmark existing depends on whether the popup is open<br> <astearns> ack schenney<br> <dbaron> 3. (from alan?) whether ::checkmark existing depends on whether the option is currently checked<br> <dbaron> (I think yes to 1 but not to 2 and 3, but we probably need to define the underlying principles.)<br> <ydaniv> schenney: for many pseudos it should return whether active or not has also privacy concerns, so we return regardless same style<br> <fantasai> Definitely no dependency on #3 -- ::checkmark is intended to be available for styling iconography in the unchecked state as well.<br> <ydaniv> ... also currently defined 4 pseudos availabe, and we can define for each case<br> <ydaniv> ... we can punt on the rest later<br> <astearns> q+<br> <ydaniv> astearns: a little concerned about having this single member mean different things for different pseudos and whether has a single true on false for different cases<br> <ydaniv> ... sometimes you want to tell whether there's a box, so I think we should take this back to the issue<br> <flackr> qq+<br> <ydaniv> ... define what this might mean per element or whether we can define something genetal<br> <astearns> ack flackr<br> <Zakim> flackr, you wanted to react to schenney<br> <ydaniv> s/genetal/general/<br> <astearns> ack astearns<br> <ydaniv> flackr: should define whether something is defined for this check and whether needs better definition, we should be talking about actual use-cases<br> <kbabbitt> +1 to flackr<br> <fantasai> +1 flackr<br> <schenney> +1<br> <ydaniv> astearns: any comments<br> <ydaniv> ... taking it back to the issue and define per element and get a clear picture first<br> <ydaniv> 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/12158#issuecomment-3005179129 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:19:45 UTC