W3C home > Mailing lists > Public > www-style@w3.org > May 2010

Re: Splitting 'display'

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 3 May 2010 10:10:58 -0700
Message-ID: <n2pdd0fbad1005031010td1cad190xbec68c2e641abfdc@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: Peter Moulder <Peter.Moulder@infotech.monash.edu.au>, www-style list <www-style@w3.org>
On Mon, May 3, 2010 at 10:06 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
> On May 3, 2010, at 9:56 AM, Tab Atkins Jr. wrote:
>> Your statement that the display:inline vs. inline-block describes
>> placement wrt inline siblings of the box" seems incorrect.  Inlines
>> and inline-blocks act the same wrt their siblings (that is, they have
>> the same display-outside value, 'inline').  The difference is that an
>> inline has display-inside:inline, which means that any initial or
>> final linebox children get merged into the lineboxes of its parent,
>> while an inline-block has display-inside:block, which doesn't do that.
> With 'display:inline-block', you also can have margin on the outside, which you don't get with 'display:inline'.

Correct.  I think I'll claim that the no-margins thing is a property
of display-inside:inline, just like width/height.  Every other
inline-flow element (inline-table, replaced elements) acts like

Received on Monday, 3 May 2010 17:11:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:45 UTC