W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: box tree terminology

From: Brad Kemper <brad.kemper@gmail.com>
Date: Fri, 1 Apr 2011 10:20:27 -0700
Cc: Alex Danilo <alex@abbra.com>, fantasai <fantasai.lists@inkedblade.net>, Alex Mogilevsky <alexmog@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <99A8A343-132F-40AA-8B14-039049F5624F@gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>

On Apr 1, 2011, at 10:04 AM, Tab Atkins Jr. wrote:

> On Fri, Apr 1, 2011 at 7:24 AM, Brad Kemper <brad.kemper@gmail.com> wrote:
>> On Mar 31, 2011, at 11:43 PM, Alex Danilo wrote:
>>>>  book:volume
>>>>  box:?
>>> box: slice
>> We already use that term for border-image. Also, it would seem a little weird to call an anonymous inline box a slice, IMO.
> I dunno, it kinda works for me.  Second best thing I've heard so far
> (behind "box layout thing").

Slices make me think of taking something that is whole and turning it into nothing but slices (as with pie, pizza, and border images). Where you end up with something that is recognizable as a whole still, but cut into pieces (before the pieces are then removed and eaten). But these sub-boxes are often existing alongside other things that aren't there from being sliced off, and don't fit the term as neatly as with the delicious border image slices. ;)

How about "child box"? An anonymous child box is often a sibling to a child element. A column is a child of a multicol element.

Perhaps that doesn't work so well as a term for page boxes, but perhaps it doesn't need to.
Received on Friday, 1 April 2011 17:21:02 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:44 UTC