Re: [csswg-drafts] [css-grid-2] Honoring the specified width/height of a subgrid (#8966)

The CSS Working Group just discussed `[css-grid-2] Honoring the specified width/height of a subgrid`, and agreed to the following:

* `RESOLVED: close no change. spec is what we intended. action to file bugs on browsers and create WPTs`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> alisonmaher: there is trhee different parts to this issue<br>
&lt;bramus> alisonmaher: first example we are in subgrid in both direcitons with width of 50px. according to spec subgrid is wlasya streched in subgridded dimensions<br>
&lt;bramus> … we like to confirm width should be ignored, given that cols are subgridded. blink stretches but webkit sets size of sg to 50px and gecko is doing combination where text is stretched but sg is 50px<br>
&lt;bramus> … width should be ignored here<br>
&lt;bramus> fantasai: yes, that ws intention of the spec<br>
&lt;bramus> alisonmaher: any more comments?<br>
&lt;bramus> astearns: action here is to file bugs for other vendors<br>
&lt;bramus> alisonmaher: in 2nd example sg is not ?? and we like to confirm ???<br>
&lt;bramus> fantasai: you only ignore alignment and sizing in the sg’d axis, not in the other axis<br>
&lt;bramus> alisonmaher: that makes sense<br>
&lt;bramus> astearns: action is to file a bug for blink<br>
&lt;bramus> alisonmaher: 3rd example the sg inline axis is not sg’d. q is should we ignore min content size of the sg and instead use the specified width 50px. this would ??? to overflow available space<br>
&lt;bramus> … geckco and webkit use specified width, while blink considers the min content size<br>
&lt;bramus> fantasai: so this is a sg, sg’d inthe block axis but not inline<br>
&lt;bramus> … you should honor the width<br>
&lt;bramus> alisonmaher: then we should file a bug as well<br>
&lt;bramus> astearns: and please add WPT for all scenarios<br>
&lt;bramus> iank_: there is mininal test cases but generally the whole subgrid area is under tested<br>
&lt;bramus> … this set of fixes on the blink side are relative major, so we want to make sure beforehand that this is the expected thing<br>
&lt;bramus> astearns: proposed resoltuion to close no change. spec is what we intended. action to file bugs on browsers and create WPTs<br>
&lt;bramus> .. objections?<br>
&lt;bramus> RESOLVED: close no change. spec is what we intended. action to file bugs on browsers and create WPTs<br>
&lt;bramus> github-both, take up https://github.com/w3c/csswg-drafts/issues/8547<br>
&lt;bramus> Sammy_Gill: this is an open ended discussion. whjile doing some prelim work on floats we found that there ar esome complexities<br>
&lt;bramus> … we want to come back to the wg and see if there has been high demand or if there are signifcatn benefits to authors<br>
</details>


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


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

Received on Tuesday, 18 July 2023 22:32:27 UTC