W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2017

Re: [whatwg] [csswg][css-display] Updated WD of CSS Display L3

From: Boris Zbarsky <bzbarsky@mit.edu>
Date: Thu, 2 Feb 2017 15:46:33 -0500
To: fantasai <fantasai.lists@inkedblade.net>, Florian Rivoal <florian@rivoal.net>
Message-ID: <edf5dfb9-e6bc-bc2d-10e6-7fc5d0263f6d@mit.edu>
Cc: WHAT Working Group <whatwg@whatwg.org>, public-review-announce@w3.org, "www-style@w3.org" <www-style@w3.org>
On 2/2/17 2:28 PM, fantasai wrote:
> On 02/02/2017 01:18 PM, Boris Zbarsky wrote:
>> OK, so if I have a flex container with two kids, a run-in and a block,
>> do I get one flex item or two flex items and why?  And
>> did that require any thought about interactions?
> You get two flex items, because being in a flex container overrides the
> outer display type of an element:
>   https://www.w3.org/TR/css-flexbox-1/#flex-items
> In other words, the run-in/inline/block distinction is ignored within a
> flex container.

Sure, but my point wasn't whether the behavior is _defined_.  It's that 
defining it requires thinking about the various cases, and having run-in 
makes for more cases to think about.

Received on Thursday, 2 February 2017 20:47:13 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:41 UTC