- From: Christian Biesinger <cbiesinger@google.com>
- Date: Tue, 5 May 2015 19:57:43 -0400
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style list <www-style@w3.org>
On Tue, May 5, 2015 at 5:19 PM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 04/06/2015 09:24 AM, Christian Biesinger wrote: >> >> Hi there, >> >> got a question about http://dev.w3.org/csswg/css-flexbox/#intrinsic-sizes >> >> It says "For each flex item, subtract its flex base size from its >> max-content contribution size" >> >> However, doesn't calculating the flex base size require laying out the >> item? I didn't think that calculating intrinsic widths should require >> layout? > > > It does in some cases, for example orthogonal flows. We changed the wording > that defines "flex base size" a bit: > > # Otherwise, <del>lay out</del> <ins>size</ins> the item into the > # available space using its used flex basis in place of its main size... > > Hopefully this should make it more clear that layout isn't required > unless it's required (to find the size). :) > > Let me know if that addresses your concern. Yes... it does. (As a sidenote, why is flex-basis: available not definite? http://dev.w3.org/csswg/css-flexbox/#definite) >> My second question is: >> "Place all flex items into lines of infinite length." >> >> If we place them on lines of infinite length, doesn't that mean we >> have just a single line? > > > As dholbert pointed out, forced page/column breaks can introduce > forced flex line breaks. Note this only happens for column flex > containers. (Forced breaks on flex items in a row get propagated > to the row.) Wait, hold on, are you saying that for @media screen (and without columns, etc) that break-after: always will be ignored for multi-line row flexboxes? -christian
Received on Tuesday, 5 May 2015 23:58:11 UTC