W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2016

Re: [whatwg] [css-display] CSS Display Review

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 20 Sep 2016 07:02:37 -0700
Message-ID: <CAAWBYDAnnsMycwVLqrg-b8ZH4sYmtEgcd17hWQZvDhx_rwbWYA@mail.gmail.com>
To: Simon Pieters <simonp@opera.com>
Cc: WHAT Working Group <whatwg@whatwg.org>, fantasai <fantasai@inkedblade.net>, Mats Palmgren <mats@mozilla.com>, "www-style@w3.org" <www-style@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Tue, Sep 20, 2016 at 1:15 AM, Simon Pieters <simonp@opera.com> wrote:
> On Tue, 20 Sep 2016 02:54:56 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote:
>> On 9/20/16 1:46 AM, Mats Palmgren wrote:
>>>
>>> Assuming that the above are the final DOM trees, then they should
>>> create exactly the same CSS boxes as if the <div> element is replaced
>>> by its (DOM) children.
>>
>>
>> That contradicts what fantasai claimed the spec says.
>>
>> Which brings me back to my claim that the spec is not clear enough: one of
>> you two is wrong, which isn't really a situation that should arise with a
>> clear spec.
>
> I have tried to clarify this in https://github.com/whatwg/html/pull/1799.

Looks like it's clarified now - the CSS side of things was very clear,
it was HTML that wasn't clear about which "child" concept it was
using. ^_^

~TJ
Received on Tuesday, 20 September 2016 14:03:29 UTC

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