W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

Re: [csswg-drafts] [css-grid] Percentage tracks and indefinite sizes

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Nov 2017 20:04:02 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-342269371-1509998641-sysbot+gh@w3.org>
The Working Group just discussed `Percentage tracks`, and agreed to the following resolutions:

* `RESOLVED: percentage tracks sized as percentage resolve the same way for columns and rows, which involves a second layout pass in some cases`

<details><summary>The full IRC log of that discussion</summary>
&lt;frremy> Topic: Percentage tracks<br>
&lt;fantasai> Github: https://github.com/w3c/csswg-drafts/issues/1921<br>
&lt;Rossen> github:https://github.com/w3c/csswg-drafts/issues/1921<br>
&lt;frremy> lajava: To keep things symmetric, we tried to add cases to resolve percentages for height of rows<br>
&lt;frremy> lajava: But we don't have min-content phase in the block direction, like we do for width<br>
&lt;frremy> lajava: So we would need to duplicate a second pass to make this work<br>
&lt;frremy> lajava: So 1st we would like this recorded clearly in the spec if that is required<br>
&lt;frremy> lajava: And all browsers would have to change their implementation<br>
&lt;frremy> florian: and why not just follow what browsers already have implemented?<br>
&lt;frremy> Rossen: the change would be relatively straighforward, it's no big deal<br>
&lt;frremy> florian: but we would possibly break content, right?<br>
&lt;frremy> Rossen: everything we do ends up breaking someone's content, I don't think this would be an issue here<br>
&lt;frremy> lajava: well, we are still unsure about what would happen in more complex cases like in orthogonal flows<br>
&lt;frremy> lajava: but at the very least it would require a second pass, once you know the intrinsic height<br>
&lt;frremy> Rossen: any opinion from Mozilla?<br>
&lt;frremy> Rossen: there is still time to fix, but window is closing<br>
&lt;frremy> dholbert: I don't have a strong opinion, and Matt hasn't commented on the issue<br>
&lt;frremy> dholbert: I don't like adding new layout steps usually<br>
&lt;frremy> Rossen: but it's easy to know if you need to do it before hand<br>
&lt;frremy> Rossen: only do it if you have percentage-sized row tracks<br>
&lt;frremy> dholbert: but if it is an orthogonal flow, you have to relayout entirely right?<br>
&lt;frremy> lajava: yes, but this already happens anyway<br>
&lt;dholbert> s/Matt/Mats/<br>
&lt;frremy> Rossen: any objection?<br>
&lt;frremy> RESOLVED: percentage tracks sized as percentage resolve the same way for columns and rows, which involves a second layout pass in some cases<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1921#issuecomment-342269371 using your GitHub account
Received on Monday, 6 November 2017 20:04:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 6 November 2017 20:04:14 UTC