- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Oct 2017 19:41:00 +0000
- To: public-css-archive@w3.org
> Here, both tracks have base size of 50px, the the free space is 150 - 50 - 50 = 50. And two tracks divide this 50px 1 to 2. But that is not what is happening. Instead, the final track size is 50px and 100px in all browsers. Indeed; this appears to be a terminology mixup. Locally in that section, "free space" is correctly defined as subtracting out only the non-flexible tracks, but the "free space" term in the grid algorithm, as you point out, has a different meaning of subtracting out *all* the base sizes. We've changed the term from "free space" to "leftover space" to be more consistent with the terminology in the Track Sizing Algorithm section. > Note that https://drafts.csswg.org/css-grid/#algo-find-fr-size is quite different from what Edge does but we could update our implementation for interop. It would be interesting to know what, exactly, those differences are. > One more part that is not entirely clear is determining the size of container. As far as I can tell, Chrome's Grid behavior is correct per spec right now, but implementations haven't yet caught up with the corresponding section in Flexbox. (We recently made some edits to this, and ended up reverting them; #1735 has the details.) ---- Let us know if there's anything left to do on this issue. (And again, we'd be interested to know about Edge's behavior for `fr`s in Grid.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1120#issuecomment-336548802 using your GitHub account
Received on Friday, 13 October 2017 19:40:47 UTC