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

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

From: fantasai <fantasai.lists@inkedblade.net>
Date: Thu, 2 Feb 2017 14:28:55 -0500
To: Boris Zbarsky <bzbarsky@mit.edu>, Florian Rivoal <florian@rivoal.net>
Message-ID: <3115ab95-c673-2611-be0b-2f45b32ad419@inkedblade.net>
Cc: WHAT Working Group <whatwg@whatwg.org>, public-review-announce@w3.org, "www-style@w3.org" <www-style@w3.org>
On 02/02/2017 01:18 PM, Boris Zbarsky wrote:
> On 2/1/17 6:07 PM, fantasai wrote:
>> Wrt this particular issue, run-ins only run into other blocks; they
>> do not exist in or affect layout modes other than block-and-inline.
>
> 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.

~fantasai
Received on Thursday, 2 February 2017 19:38:34 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 2 February 2017 19:38:34 UTC