- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Jan 2025 19:35:51 +0000
- To: public-css-archive@w3.org
Yeah the latest published thing is from 2018, so I'm calling it old. > always goto the latest draft to verify things I mean, not always. But if you want to discuss the spec details, then looking at an old thing isn't much productive. > what's the value of the published version? See https://www.w3.org/policies/process/#maturity-stages. In particular, editor's drafts are lacking in some areas: > [Working Groups](https://www.w3.org/policies/process/#GroupsWG) and [Interest Groups](https://www.w3.org/policies/process/#GroupsIG) may make available [Editor’s drafts](https://www.w3.org/policies/process/#editors-draft). Editor’s drafts (ED) have no official standing whatsoever, and do not necessarily imply consensus of a [Working Group](https://www.w3.org/policies/process/#GroupsWG) or [Interest Group](https://www.w3.org/policies/process/#GroupsIG), nor are their contents endorsed in any way by W3C. > So point [9.2(4)](https://www.w3.org/TR/css-flexbox-1/#algo-main-container) is effectively goto [9.2(2)](https://www.w3.org/TR/css-flexbox-1/#algo-available) when the flex container has an indefinite size to make it definite ? Seems like that could be it. Not sure if it's clearly explained somewhere, I'm not that familiar with the flexbox spec, I know grid better (explained in https://drafts.csswg.org/css-grid/#layout-algorithm) Note re-resolving percentages isn't specific of flexbox/grid, it's the same for the contents of an inline-block (in the inline axis only). -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11392#issuecomment-2569721607 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 19:35:53 UTC