- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jan 2022 21:51:22 +0000
- To: public-css-archive@w3.org
> /cc @fantasai and @dholbert who appear to have developed this algorithm originally In my recollection, I can't take credit for developing the spec's current intrinsic sizing algorithm (and we haven't actually implemented it in Firefox yet), though I think I did offer feedback when it was being written. As I recall: at a high level the algorithm here is just trying to reverse-engineer what the flexbox layout algorithm *actually does*, in order to produce an intrinsic size that lets each flex item achieve its own max-content size. So the correct wording here would be whatever achieves that result. (And given that the flexbox layout algorithm primarily uses the `scaled flex shrink factor` -- and only uses the `flex shrink factor` **in order to compute the `scaled flex shrink factor`** -- my gut feeling is that it wouldn't be correct to swap one for the other here.) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6909#issuecomment-1009378118 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 January 2022 21:51:23 UTC