- From: Greg Whitworth <gwhit@microsoft.com>
- Date: Wed, 2 Dec 2015 22:13:42 +0000
- To: Daniel Holbert <dholbert@mozilla.com>, Christian Biesinger <cbiesinger@google.com>, Tab Atkins Jr. <jackalmage@gmail.com>
- CC: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
>On 12/02/2015 01:44 PM, Greg Whitworth wrote: >>>> Your testcase doesn't invoke max-content at all. Your desired >>>> result is what you get, yes, but from elsewhere in the algorithm, as >>>> fantasai outlined. >>> >>> Huh? Why do you say that? It's an inline-flex, therefore >>> shrink-wrapped, therefore should be sized at max-content. No? >>> >>> Yet the border/background-color is only around the first column in >>> blink, right now. >>> >>> -Christian >> >> Yep I'm confused by Blink's result here, even Firefox's (adding Daniel for >insight). > >Firefox's current intrinsic-width calculation for a wrapping column-oriented >flexbox is known-naive/wrong. That's filed here: > https://bugzilla.mozilla.org/show_bug.cgi?id=995020 > >Looks like https://code.google.com/p/chromium/issues/detail?id=507397 is >filed on the similar issue for Chrome (and seems to be what prompted biesi to >start this thread). > >~Daniel Ok, to speak to his question then: The main size determination states: # Otherwise, starting from the first uncollected item, collect consecutive items one by one until the first time that the next collected item would not fit # ** into the flex container’s inner main size ** (or until a forced break is encountered, see §10 Fragmenting Flex Layout). # If the very first uncollected item wouldn’t fit, collect just it into the line. Isn't this stating to take the constraints of the main size into account? Thus max-height in the case of a column flex container?
Received on Wednesday, 2 December 2015 22:14:15 UTC