W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css-display] Unofficial draft of a Display spec ready for consumption

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 23 Oct 2012 09:43:21 -0700
Message-ID: <CAAWBYDBBEnSwsGgBva0NNtdEi-vpMB2H+bP5Xn-8YyhcAhkyaA@mail.gmail.com>
To: Simon Sapin <simon.sapin@kozea.fr>
Cc: Andrew Fedoniouk <news@terrainformatica.com>, www-style list <www-style@w3.org>
On Tue, Oct 23, 2012 at 9:26 AM, Simon Sapin <simon.sapin@kozea.fr> wrote:
> Le 23/10/2012 18:12, Tab Atkins Jr. a écrit :
>> Multicol is a legacy mistake, but all we have to do is say that the
>> multicol properties only apply in block layout, and we're good.  This
>> was difficult to do before, because we wanted to be able to use them
>> in "block", "inline-block", "list-item", "table-cell", and
>> "table-caption" - this seems like a random set when all you have is
>> the 'display' property.  In the new model, these all have the common
>> property of using block layout (display-inside: block;), so it's easy
>> to specify the multicol limitation.
> Sorry to side-track, but is "using block layout" the same as what CSS 2.1
> calls "being a block container"?

In the terminology I'm using, it's "has display-inside:block;", but I
think it's the same as "being a block container", yes.  I'll need to
verify as I fill out the draft a bit more.

Received on Tuesday, 23 October 2012 16:44:10 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:05 UTC