Re: [csswg-drafts] [css-lists] Interaction of ::marker with other pseudo-elements. (#3826)

The CSS Working Group just discussed `::marker vs other pseudo-elements`, and agreed to the following:

* `RESOLVED: don't expand the list of props that apply to ::marker`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: ::marker vs other pseudo-elements<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/3826<br>
&lt;fantasai> I agree with https://github.com/w3c/csswg-drafts/issues/3826#issuecomment-483320040<br>
&lt;fantasai> emilio: I think there was some confusion of whether 'display' applies to markers<br>
&lt;fantasai> fantasai: display doesn't currently apply to markers<br>
&lt;fantasai> fantasai: and I don't think it should until marker layout is fully defined<br>
&lt;fantasai> fantasai: and its interaction with display is also defined<br>
&lt;fantasai> TabAtkins: Mats is arguing for much more than display<br>
&lt;fantasai> TabAtkins: He's arguing for marker to take all properties, like ::before/::after<br>
&lt;fantasai> TabAtkins: Is there a reason to stop at display or re-litigate after?<br>
&lt;dbaron> ScribeNick: florian<br>
&lt;florian> fantasai: the reason we have a limited list of properties is that because we don7t know how marker layout works<br>
&lt;florian> fantasai: so allowing these properties without knowing what they do is bad<br>
&lt;florian> fantasai: we also don't know the size of the box, so any property that makes that visible is a problem<br>
&lt;florian> fantasai: we don't know if line-height plays a role... many other properties have the problem<br>
&lt;florian> fantasai: there are implementation specific answers, but so far they're not exposed<br>
&lt;florian> fantasai: so if we expose them, me might accidentally lock compat on whatever ships first<br>
&lt;florian> fantasai: so we should not<br>
&lt;florian> emilio: makes sense to me, will apply that to firefox<br>
&lt;florian> fantasai: for now we just allow text related properties<br>
&lt;florian> fantasai: eventually we want to relax that, but only after layout is defined<br>
&lt;fantasai> https://www.w3.org/TR/css-pseudo-4/#marker-pseudo<br>
&lt;florian> proposed resolution: don't expand the list of props that apply to ::marker<br>
&lt;florian> RESOLVED: don't expand the list of props that apply to ::marker<br>
&lt;fantasai> It would probably be OK to add more properties from css-text/text-decor<br>
&lt;fantasai> those that apply to inlines<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/3815<br>
&lt;emilio> github: https://github.com/w3c/csswg-drafts/issues/3826<br>
</details>


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

Received on Wednesday, 8 May 2019 16:43:29 UTC