Re: [csswg-drafts] [css-pseudo-4] should CSSPseudoElement have a pseudo() method? (#3836)

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>
&lt;fantasai> Topic: CSSPseudoElement having a pseudo() method<br>
&lt;fantasai> AmeliaBR: Seems to make sense to me, if a pseudo-element can have a pseudo-element, then having .pseudo() would make sense<br>
&lt;fantasai> emilio: Have we decided yet how to make those styleable<br>
&lt;fantasai> fantasai: will be stylable with selectors like ::before::marker<br>
&lt;fantasai> emilio: I would wait to add this method until that is allowed<br>
&lt;fantasai> fantasai: So proposal is to add .pseudo() to CSSPseudoElement once stacked pseudo becomes a valid selector<br>
&lt;fantasai> plinss: Side issue of whether to rename .element to .parent<br>
&lt;fantasai> fantasai: Not always a parent<br>
&lt;fantasai> TabAtkins: The full term is "originating element" but that was too long<br>
&lt;fantasai> TabAtkins: So shortened to .element<br>
&lt;fantasai> plinss: Need to reach pseudo-element between you and the element<br>
&lt;fantasai> TabAtkins: Yeah, that's what .element would do<br>
&lt;fantasai> plinss: OK<br>
&lt;fantasai> TabAtkins: When we adopt this, just the return type would be adapted<br>
&lt;fantasai> RESOLVED: add .pseudo() to CSSPseudoElement once some stacked pseudo combination becomes a valid selector. Adjust .element return type to match.<br>
&lt;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