- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Apr 2025 19:27:46 +0000
- To: public-css-archive@w3.org
> It's defined in https://drafts.csswg.org/css-flexbox-1/#intrinsic-sizes, it should work for both axes. 1. When the block-size is in the cross direction: [Section 9.9.2. Flex Container Intrinsic Cross Sizes](https://drafts.csswg.org/css-flexbox-1/#intrinsic-cross-sizes) applies. However, this section does not distinguish between `min-content` and `max-content` sizes, contrary to what the comments in my initial message suggest. 2. When the block-size is in the main direction: [Section 9.9.1. Flex Container Intrinsic Main Sizes](https://drafts.csswg.org/css-flexbox-1/#intrinsic-main-sizes) applies. Specifically, the ["ideal algorithm"](https://drafts.csswg.org/css-flexbox-1/#intrinsic-main-sizes-ideal) notes: > "The min-content main size of a single-line flex container is calculated identically to the max-content main size, except that the flex items’ min-content contributions are used instead of their max-content contributions." However, it's unclear what the actual difference is—if any—between the `max-content` and `min-content` contributions of a flex item when block-size is involved. 3. [Section 9.9.3. Flex Item Intrinsic Size Contributions](https://drafts.csswg.org/css-flexbox-1/#intrinsic-item-contributions) explicitly refers only to the main size. When the inline size is the main direction and block size is the cross direction, it’s unclear how this section applies to block-size. If the instructions are indeed meant to apply to both axes, then using “main size” is misleading, and the spec should explicitly state that the logic applies to both dimensions. -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12108#issuecomment-2822277873 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 22 April 2025 19:27:47 UTC