- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Jan 2019 22:32:20 +0000
- To: public-css-archive@w3.org
Basically yes, but IMO the sentence would bee too long and a bit confusing, there is already a min/max-content dichotomy for the size constraint, one could think that the this min/max-content is refers to that. I would prefer a refactoring like > If the track has an `auto` min track sizing function, set the track’s base size to the maximum of its items’ foobars. > The ***foobar*** of an item is calculated as follows: > 1. Let *max* be the max track sizing function if that is fixed, else the min/max-content contribution if the max track sizing function is `min/max-content`, respectively, else infinity. > 2. If the grid container is being sized under a min/max-content constraint, return the item’s min/max-content contribution, respectively, limited by *max* and floored by the item’s minimum contribution. > 3. Return the item’s minimum contribution, floored at zero. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3565#issuecomment-458734228 using your GitHub account
Received on Tuesday, 29 January 2019 22:32:21 UTC