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

Re: [csswg-drafts] [css-grid] Reconsider the meaning of 1fr

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Sep 2017 16:45:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-329227763-1505321150-sysbot+gh@w3.org>
The Working Group just discussed `Reconsider the meaning of 1fr`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Reconsider the meaning of 1fr<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1777<br>
&lt;dael> fantasai: There were good comments. I need to dig through those. So, thanks for commenting.<br>
&lt;dael> astearns: Does anyone have an opinion that has not commented on github?<br>
&lt;dael> TabAtkins: I haven't dug deep. I need to spend time thinking about it.<br>
&lt;dael> jensimmons: I'd like to have an opinion, but I feel like I need examples to understand impl and I haven't done that.<br>
&lt;tantek> Without having looked into it deeply, I would tend to go with with Rachelandrew's analysis<br>
&lt;dael> fantasai: Right now, as overview, min size of a grid container can take starts with min track sizing and if there's extra space the tracks will expand until reach max. Right now fr has an impl min of auto which by default is the min content, but if they have min width or height it uses that. Max track is the flex unit.<br>
&lt;dael> fantasai: Same is true in height. Proposal is instead of using min for fr, we use 0 so content will overflow track if it can't shrink to 0<br>
&lt;dael> TabAtkins: Reason for current is it matches with flexbox. If you say flex 1 you start with min-width of auto. This works the same way unles syou override<br>
&lt;dael> fantasai: Where this becomes confusing is when they use track sizing for a large amt of content which they expect to get clipped or shrink and we're enforcing a min on that countent.<br>
&lt;dael> TabAtkins: I feel it's a lot like the confusing part of flexbox where the min of height is the auto and that's something larger then intended.<br>
&lt;dael> TabAtkins: It's the blow up in a good way where you don't lose anything, but it's unexpected.<br>
&lt;dael> TabAtkins: This is exactly us porting the flexbox<br>
&lt;dael> fantasai: That's the background. We can all look more deeply and discuss on GH<br>
&lt;dael> astearns: Thanks to rachelandrew and fremy for already commenting there.<br>
&lt;dael> astearns: Anything else on this?<br>
&lt;dael> jensimmons: Thanks for the info, that makes it clear. My first take is I hesitate to do this b/c the way fr works right now is incredibly useful. I can see the want, btu I don't know if it's right. We'd break stuff if we do this, but the way it's written is also the most useful way to use fr.<br>
&lt;dael> jensimmons: I think education may be right instead of a change.<br>
&lt;dael> astearns: Thanks jensimmons. Sounds like we should have a few more examples in the issue going through impl of actual email.  I think we should take this to GH and come back in a week or two.<br>
&lt;dael> astearns: I believe that's it for the agenda.<br>
&lt;dael> astearns: Reminder TPAC is coming. Register before Oct 7 to get the lower price. Anything else for the agneda this week?<br>
&lt;dael> astearns: Everyone gets 15 minutes back!<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1777#issuecomment-329227763 using your GitHub account
Received on Wednesday, 13 September 2017 16:45:53 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:18 UTC