Re: [csswg-drafts] [css-grid-1] Application of grid-positioning properties to static position of grid children is inconsistent (#7661)

The CSS Working Group just discussed `[css-grid-1] Application of grid-positioning properties to static position of grid children is inconsistent`, and agreed to the following:

* `RESOLVED: Go with the content-box (option 2)`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> summary -> https://github.com/w3c/csswg-drafts/issues/7661#issuecomment-1587880994<br>
&lt;emilio> iank_: restating previous conversations. Two options: always use content-box, or always use grid-positioning properties<br>
&lt;emilio> ... two weeks ago people were asking for use cases<br>
&lt;emilio> ... I don't think anybody came back with use cases for always using grid-positioning<br>
&lt;emilio> ... me and tab have a preference for content-box, fantasai has a preference for using the properties<br>
&lt;emilio> fantasai: we have agreement on if the grid properties are auto then we use the content-box<br>
&lt;emilio> iank_: that might be more complicated because of how those work<br>
&lt;emilio> ... because those insert additional lines for the purposes of abspos<br>
&lt;emilio> ... so would like to keep that separate<br>
&lt;emilio> Rossen_: so we want to go with option (2), which is always use content-box (option (1) is off the table)<br>
&lt;emilio> q+<br>
&lt;emilio> iank_: I'd like to propose going for (2), I don't think there are use cases for (3)<br>
&lt;Rossen_> q+<br>
&lt;Rossen_> ack emilio<br>
&lt;TabAtkins> emilio: Echo slight support for going for the content box<br>
&lt;fantasai> scribe+ TabAtkins<br>
&lt;chrishtr> +1 to option 2 (content box)<br>
&lt;TabAtkins> emilio: Seems there's no use-cases for grid, seems determining the static position form grid porpertiers can be a rabbit hole of interop not worth getting into<br>
&lt;TabAtkins> emilio: If always using the content box works, then good<br>
&lt;emilio> Rossen_: quick q. also supportive of option (2) tho. If you want an annotation on the box that sits on top of everything else like a semi-transparent number<br>
&lt;TabAtkins> Rossen_: qq, if you wanted an annotation on the box that sits on top of everything else, like a semi-transparent number<br>
&lt;emilio> ... let's say you want to number your grid cells<br>
&lt;emilio> ... is my assumption correct that if you want to achieve the same effect you'd have to say which line you're positioning to in the grid and then use that as your left and top?<br>
&lt;emilio> iank_: right you need to make the grid the containing block yeah, and set top: 0 left: 0<br>
&lt;emilio> Rossen_: what about auto placement? Where would that end up?<br>
&lt;emilio> iank_: you can't (today) setting auto placement on an abspos, you'd need to wrap it in a grid item<br>
&lt;emilio> Rossen_: can we make that the default behavior?<br>
&lt;emilio> iank_: we don't invoke auto placement for out of flows<br>
&lt;emilio> ... you need to be explicit to pick up the grid area<br>
&lt;emilio> Rossen_: ok in that case I'm good with option 2 as well<br>
&lt;emilio> RESOLVED: Go with the content-box (option 2)<br>
&lt;emilio> iank_: final note: we'll do this change behind a kill-switch in case people rely on the weird behavior, can come back to the group if the change goes wrong<br>
</details>


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


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

Received on Wednesday, 14 June 2023 16:29:53 UTC