- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Fri, 08 Dec 2023 22:58:50 +0000
- To: public-css-archive@w3.org
The logic behind that is meant to be the same everywhere where `<flex>` values can be used. From the [general definition](https://drafts.csswg.org/css-grid-2/#:~:text=%3Cflex%3E%20values%20between%200fr%20and%201fr): > `<flex>` values between `0fr` and `1fr` have a somewhat special behavior: when the sum of the flex factors is less than 1, they will take up less than 100% of the leftover space. > … > However, if the tracks request less than the full amount (such as three tracks that are each `.25fr`) then they’ll each get exactly what they request (25% of the leftover space to each, with the final 25% left unfilled). > … > This pattern is required for continuous behavior as `fr` values approach zero (which means the tracks wants none of the leftover space). So `0fr` won't take up any leftover space. Though the definition you quoted above [came from](https://github.com/w3c/csswg-drafts/pull/7029/commits/1f982db53e0386f21f986fa898cca8585d70a562#diff-994978825958ad4d2d852734a8d7d222a30c4bb14402ef0bb98905805bd763a3R1941-R1947) @tabatkins. So maybe he can decide whether to remove it or adjust it to align it with the general definition. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9666#issuecomment-1847949020 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 8 December 2023 22:58:52 UTC