Re: [csswg-drafts] [selectors-4] Need to allow stacked pseudo-element selectors in the grammar (#3876)

The CSS Working Group just discussed `Need to allow stacked pseudo-element selectors in the grammar`, and agreed to the following:

* `RESOLVED: Generic selector grammar allows stacking pseudo elements and classes. Only certain combos will be made valid, by default everything is invalid`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Need to allow stacked pseudo-element selectors in the grammar<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3876<br>
&lt;dael> Rossen_: Is TabAtkins on?<br>
&lt;TabAtkins> Will be in a sec<br>
&lt;dael> fantasai: I can take it<br>
&lt;florian> I did not check that TabAtkins did the grammar correctly (I assume he did), but I support the intent.<br>
&lt;dael> fantasai: There were some cases where we had pseudo elements that are pseudo elements of pseudo elements. One is the marker of a before pseudo if that's set as display:list-item<br>
&lt;dael> fantasai: Selectors grammar only allows one in the grammar. We'll have to relax to allow this. Proposal is do it same as pseudo classes applied to pseudo elements. It's generically allow, but disallowed except for certain whitelisted combinations<br>
&lt;dael> fantasai: The generic grammar needs to allow forthe stacking. Proposal here is to do that for pseudo elements so one can allow another to stack after<br>
&lt;dael> amelia: Really a need to make the whitelist or defined at individual level. It could be a valid that doesn't match anything. Example is invalid that doesn't match anyway and wouldn't when on a before or after.<br>
&lt;amelia> s/match anyway/match non-form elements anyway/<br>
&lt;dael> fantasai: Reason to do is b/c at some point in future might allow some combos, but not sure which will become reasonable. better to make them invalid now and only the ones that make sense now are valid. When another combo is reasonable in the future we can say it's now valid and meanssomething.<br>
&lt;dael> fantasai: Don't want a selector that's valid now but matches nothing but 5 years from now it starts matching a bunch of stuff<br>
&lt;dael> Rossen_: Sounds reasonable<br>
&lt;dael> Rossen_: Other points?<br>
&lt;Rossen_> s/whitelist/allow-list/<br>
&lt;dbaron> sounds reasonable to me too, though I'm not sure I could extract all that fro mthe issue<br>
&lt;dael> Rossen_: +1 to dbaron comment. Thanks for making it clear fantasai<br>
&lt;dael> Rossen_: Objections to accepting the issue?<br>
&lt;dael> fantasai: Prop: Generic selector grammar allows stacking pseudo elements and classes. Only certain combos will be made valid, by default everything is invalid<br>
&lt;dael> Rossen_: Objections?<br>
&lt;dael> RESOLVED: Generic selector grammar allows stacking pseudo elements and classes. Only certain combos will be made valid, by default everything is invalid<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3876#issuecomment-488482816 using your GitHub account

Received on Wednesday, 1 May 2019 23:12:17 UTC