- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Dec 2024 09:40:51 +0000
- To: public-css-archive@w3.org
Regarding point [4](https://www.w3.org/TR/css-flexbox-1/#algo-main-container) in the same section: > Determine the main size of the flex container using the rules of the formatting context in which it participates. For this computation, auto margins on flex items are treated as 0. It’s unclear why this step appears after calculating the flex base size and hypothetical main size of each item. Excluding the note about the automatic block size of a block-level flex container, this instruction seems more appropriate in point [2](https://www.w3.org/TR/css-flexbox-1/#algo-available), as the flex container's definite main size establishes the available main space for the flex items. Perhaps the intention here is to determine the main size of an indefinite flex container based on the sum of the hypothetical main sizes of its flex items? -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11392#issuecomment-2553208683 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 December 2024 09:40:52 UTC