- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Sun, 20 Apr 2025 23:14:21 +0000
- To: public-css-archive@w3.org
> No. This is not true for flex containers nor ~grid containers. No browser follows the spec, though. > > See example in [#6457 (comment)](https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-908733927) I suspect no browser follows the spec because its wording is overly convoluted. For example, in the grid section you [cited](https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-908733927), it [states](https://drafts.csswg.org/css-grid/#algo-grow-tracks): > “For the purpose of this step: if sizing the grid container under a max-content constraint, the free space is infinite; if sizing under a min-content constraint, the free space is zero.” Then it defines: >max-content constraint: a sizing constraint imposed by the box’s containing block that causes it to produce its max-content contribution. >min-content constraint: a sizing constraint imposed by the box’s containing block that causes it to produce its min-content contribution. But how can the grid container’s *own* containing block impose a constraint *on itself*? It’s unclear. A much clearer wording would be: > “For the purpose of this step: if the grid container’s inline or block size is `max-content`, the free space is infinite; if it is `min-content`, the free space is zero.” The flexbox spec isn’t any clearer. In [section 9.9.2 “Flex Container Intrinsic Cross Sizes”](https://www.w3.org/TR/css-flexbox-1/#intrinsic-cross-sizes), it doesn’t distinguish between `min-content` and `max-content` sizing along the cross axis. Instead, it delegates sizing to the flex items—which themselves may be flex, grid or block containers—so the only meaningful difference ends up being the grid container’s space‑distribution nuances. cc @fantasai -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12103#issuecomment-2817382960 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 20 April 2025 23:14:22 UTC