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

[csswg-drafts] [css-grid] Unclear which "flexible track" is used when finding the used flex fraction (#4544)

From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Nov 2019 11:27:15 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-529286934-1574854034-sysbot+gh@w3.org>
Loirooriol has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-grid] Unclear which "flexible track" is used when finding the used flex fraction ==
https://drafts.csswg.org/css-grid/#algo-flex-tracks defines how to find the "used flex fraction":

> First, find the used flex fraction: [...]
> The used flex fraction is the maximum of:
> -  **If the flexible track’s flex factor** is greater than one, the result of dividing the track’s base size by its flex factor; otherwise, the track’s base size.
> -  The result of finding the size of an fr for each grid item that crosses a flexible track, using all the grid tracks that the item crosses and a space to fill of the item’s max-content contribution.

It's confusing when the definition says "the flexible track’s flex factor". Which flexible track? If you don't look at https://drafts.csswg.org/css-grid/#flex-fraction, this can make it seem like each track has it's own flex fraction or something.

I think it would be clearer like this:

> First, find the **grid**'s used flex fraction: [...]
> The used flex fraction is the maximum of:
> -  **For each flexible track,** if the track’s flex factor is greater than one, the result of dividing the track’s base size by its flex factor; otherwise, the track’s base size.
> -  **For each grid item that crosses a flexible track**, the result of finding the size of an fr using all the grid tracks that the item crosses and a space to fill of the item’s max-content contribution.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4544 using your GitHub account
Received on Wednesday, 27 November 2019 11:27:16 UTC

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