- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 May 2019 16:36:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `CSSPseudoElement having a pseudo() method`, and agreed to the following: * `RESOLVED: add .pseudo() to CSSPseudoElement once some stacked pseudo combination becomes a valid selector. Adjust .element return type to match.` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: CSSPseudoElement having a pseudo() method<br> <fantasai> AmeliaBR: Seems to make sense to me, if a pseudo-element can have a pseudo-element, then having .pseudo() would make sense<br> <fantasai> emilio: Have we decided yet how to make those styleable<br> <fantasai> fantasai: will be stylable with selectors like ::before::marker<br> <fantasai> emilio: I would wait to add this method until that is allowed<br> <fantasai> fantasai: So proposal is to add .pseudo() to CSSPseudoElement once stacked pseudo becomes a valid selector<br> <fantasai> plinss: Side issue of whether to rename .element to .parent<br> <fantasai> fantasai: Not always a parent<br> <fantasai> TabAtkins: The full term is "originating element" but that was too long<br> <fantasai> TabAtkins: So shortened to .element<br> <fantasai> plinss: Need to reach pseudo-element between you and the element<br> <fantasai> TabAtkins: Yeah, that's what .element would do<br> <fantasai> plinss: OK<br> <fantasai> TabAtkins: When we adopt this, just the return type would be adapted<br> <fantasai> RESOLVED: add .pseudo() to CSSPseudoElement once some stacked pseudo combination becomes a valid selector. Adjust .element return type to match.<br> <emilio> github: https://github.com/w3c/csswg-drafts/issues/3836<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3836#issuecomment-490559213 using your GitHub account
Received on Wednesday, 8 May 2019 16:36:10 UTC