- From: gitspeaks via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jan 2025 18:36:20 +0000
- To: public-css-archive@w3.org
> There are things like fit-content and stretch. How are these values applicable in this context? The specification for [flex-basis](https://www.w3.org/TR/css-flexbox-1/#flex-basis-property) lists its possible values as `'content | <'width'>` with an initial value of `auto`. The link for [<'width'>](https://www.w3.org/TR/CSS21/visudet.html#propdef-width) which directs to the CSS 2.1 specification defines the valid values as: `<length> | <percentage> | auto | inherit`. >Your testcase doesn't show that. Flex items can re-resolve their percentages after the final size of the flex container is known. What do you mean it doesn't show that? Here is the render from the current version of Chrome: ![render](https://github.com/user-attachments/assets/e64ccc6c-a2fe-4686-b8cb-4203ea14dbfe) Clearly, this is *not* resolved as `max-content`. > Flex items can re-resolve their percentages after the final size of the flex container is known. Are you suggesting that a flex container sized under `min-content` or `max-content` transitions from indefinite to definite size mid-algorithm, causing the layout algorithm to restart? Where is this behavior specified in the [algorithm details](https://www.w3.org/TR/css-flexbox-1/#layout-algorithm)? -- GitHub Notification of comment by gitspeaks Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11392#issuecomment-2569656565 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 January 2025 18:36:21 UTC