Re: [csswg-drafts] [css-sizing] need to be clear about inputs to computation of min-content, max-content, and fit-content sizes

For second bullet point, *hopefully* we can define that the available other-axis space is always either (a) fixed, or (b) infinite, with "fixed" meaning "a length", or "definite", or something in-between. Generally speaking, "fixed" should be trivially determinable from the tree, so any calling code (that is, layout algos that ask for an intrinsic size) don't have to provide an other-axis available space themselves.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2890#issuecomment-420082478 using your GitHub account

Received on Monday, 10 September 2018 22:28:37 UTC