Re: [csswg-drafts] [css-display][css-pseudo] Is ::marker created by display:list-item or does it always exist?

The Working Group just discussed `Is ::marker created by display:list-item or does it always exist?`, and agreed to the following resolutions:

* `RESOLVED: marker exists on all elements, on ::before and on ::after but no box unless it's display: list-item`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:  Is ::marker created by display:list-item or does it always exist?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1793<br>
&lt;dael> TabAtkins: We all agree on overall behavior. More a question what model we want. Marker pseudo element. Original question is decided. It was what things in theory can have marker pseudo elements. It's only created by thing with display list item. Theoretical model of the element tree, which things have the display list item.<br>
&lt;dael> TabAtkins: We wanted approval that  marker elements always existing hte box tree on eleemnts before or after and they're auto surpressed.<br>
&lt;dael> TabAtkins: Other options are if they exist in the tree depends on style or say they always exist but not on elements but not on pseudo elements ::before or ::After which breaks the current behavior for FF and Chrome.<br>
&lt;dael> TabAtkins: Final option is marker elements always exist and can be on any tree abiding elements. This could mean that market pseudos contain marker pseudos. Because you can't set display on them you'll never see them.<br>
&lt;dael> TabAtkins: Depends on the theoretical model you want.<br>
&lt;dael> emilio: Is that required? Except for slotted I think most browsers reject pseudo elements at parsing time.<br>
&lt;dael> TabAtkins: Does not require that.<br>
&lt;dael> TabAtkins: That would be good if you actual style mested marker.<br>
&lt;dael> emilio: It would mean you can set content-before.<br>
&lt;dael> TabAtkins: Ideally you should be able to, but right now you have an unstylable marker.<br>
&lt;dael> dbaron: Auto-surpressed?<br>
&lt;dael> TabAtkins: Like how ::before doesn't create a box unless it's non-none. Marker wouldn't have a box unless it's contents had display.<br>
&lt;dael> dbaron: Is there a distinction between exists and surpressed and not existing?<br>
&lt;dael> TabAtkins: One is a layer violation. It requires us to not completely build on the tree until we resolve the styles. Right now we can build the element tree fully. This is theoretical design and has no practical considerations.<br>
&lt;dael> TabAtkins: We suggest they always exist on elements, ::before and ::after<br>
&lt;dael> fremy: is that all browsers do?<br>
&lt;dael> TabAtkins: THose are all that browsers have always there. If we add more we can categorize properly.<br>
&lt;dael> TabAtkins: Objections to my preferred option that marker exists on all elements, on ::before and on ::after but no box unless it's displayed.<br>
&lt;dbaron> s/displayed/display: list-item/<br>
&lt;dael> florian: If you display list-item...the initial value of content is normal then you get it but if you don't display list item is it like a ::before?<br>
&lt;dael> TabAtkins: It does not show up.<br>
&lt;dael> Rossen: Obj?<br>
&lt;dbaron> sounds good to me<br>
&lt;dael> RESOLVED: marker exists on all elements, on ::before and on ::after but no box unless it's display: list-item<br>
</details>


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

Received on Thursday, 12 April 2018 10:52:06 UTC