Re: [csswg-drafts] [css-display] Add 'display:contents list-item' ? (#4022)

The CSS Working Group just discussed `display: contents list-item`, and agreed to the following:

* `RESOLVED: close wontfix`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: display: contents list-item<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/4022<br>
&lt;fantasai> astearns: Proposal is close wontfix?<br>
&lt;fantasai> TabAtkins: brought up that there's nothing theoretically wrong with 'display: contents list-item' which would generate a ::marker<br>
&lt;fantasai> TabAtkins: Currently the grammar doesn't allow combining these two<br>
&lt;fantasai> TabAtkins: My objection to this is just that we don't have any particularly strong reason to do so<br>
&lt;fantasai> TabAtkins: but there's nothing wrong with it<br>
&lt;fantasai> TabAtkins: so suggesting close no change<br>
&lt;fantasai> TabAtkins: but no objection to making it possible if someone thinks this is a useful thing that we should allow<br>
&lt;fantasai> astearns: My case in the comments is completely theoretically<br>
&lt;fantasai> TabAtkins: I can see it, but I think it's one more thing that we don't necessarily need<br>
&lt;fantasai> emilio: seems like one more case that we should avoid, so ok with no change<br>
&lt;fantasai> astearns: Any objections to no change?<br>
&lt;fantasai> RESOLVED: close wontfix<br>
&lt;emilio> s/case that we should/edge case we should<br>
&lt;fantasai> astearns: If Mats feels strongly, he could reopen it<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 August 2021 16:48:25 UTC