- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Feb 2019 17:46:15 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Grid (base sizes and growth length)`. <details><summary>The full IRC log of that discussion</summary> <fremy> Topic: Grid (base sizes and growth length)<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/3646<br> <fremy> oriol: there are two issues in there<br> <fremy> oriol: one is that when sizing a grid under max-content constraint<br> <fremy> oriol: when computing the space for item with intrinsic size<br> <fremy> oriol: we only consider the base size of tracks<br> <fremy> oriol: which can be smaller than the size of the track in the end<br> <fremy> oriol: so, maybe we should consider instead of the contribution of the item minus the track size<br> <fremy> oriol: consider the contribution of the item minus the growth limit<br> <fremy> oriol: (explains the example in the issue)<br> <fremy> oriol: when the growth limit of a track increases, we could increase to base size up to that growth limit<br> <fremy> oriol: this means that when you are using fit-content<br> <fremy> oriol: you need to do first min-content then max-content<br> <fremy> oriol: this is a lot of work<br> <fremy> oriol: but chromium isn't doing this all the time<br> <fremy> oriol: they perform a single layout track, and sets a base size of the tracks which is the min-content, and the growth-limit is the max-content<br> <fremy> oriol: which is ok if there are no spanning items, but if there are spanning items the result is wrong<br> <fremy> oriol: however, with my proposal, we wouldn't need to keep track of different base sizes for these two cases, and therefore we can always do only one single layout for fit-content<br> <fremy> oriol: (one single *extra* layout pass)<br> <fremy> astearns: thanks oriol<br> <fremy> astearns: some people in the room are reviewing this in a bit more details<br> <fremy> astearns: anyone has a response?<br> <fremy> astearns: or should we continue this in the issue?<br> <fremy> rego: one question, are we sure that what the change is what authors would expect?<br> <fremy> rego: if it is, I think the change oriol proposed should get done, but maybe it isn't what authors expect, I'm not sure<br> <fremy> astearns: jensimmons_ ? do you have an opinion?<br> <fremy> jensimmons_: not yet<br> <fremy> Rossen: the issue is fairly new<br> <fremy> Rossen: maybe we need to take more time<br> <tantek> TBH I can't visualize this. Any chance of projecting an example for things like this? E.g. before/after change?<br> <bkardell_> tantek, yes please<br> <fremy> Rossen: maybe we can use whiteboards at lunch<br> <florian> I am a little confused. Does that relate to https://github.com/w3c/csswg-drafts/issues/2356 ?<br> <fremy> fantasai: I'm in favor of that<br> <fremy> fantasai: but I would also desire to publish a new grid update<br> <fremy> fantasai: so I'm classifying changes between big changes and minor fixes<br> <fremy> fantasai: and I would want to first get to the changes that are just fixes<br> <fremy> fantasai: and continue to work on bigger changes on a more relaxed timeline<br> <fremy> rachelandrew: is that just a perf issue?<br> <fremy> rego: well, I mean, not entirely<br> <fremy> rego: but it would enable firefox to match both the spec and chrome, because in Chrome we don't follow the spec because it's both faster and easier not to follow it<br> <fantasai> s/but I would also desire/Wrt the labels, I want/<br> <fremy> rego: with the proposed change, we could both update to this new text<br> <tantek> (wants what Jen Simmons said minuted, but can't remember exactly to type it himself)<br> <jensimmons_> I said: Let’s figure this out. It should make sense for Authors. And we want to squash any interop problems…. yes.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3646#issuecomment-467961004 using your GitHub account
Received on Wednesday, 27 February 2019 17:46:16 UTC