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

RE: box tree terminology

From: Alex Mogilevsky <alexmog@microsoft.com>
Date: Thu, 31 Mar 2011 19:23:00 +0000
To: fantasai <fantasai.lists@inkedblade.net>
CC: "www-style@w3.org" <www-style@w3.org>
Message-ID: <D51C9E849DDD0D4EA38C2E539856928411F0F883@TK5EX14MBXC213.redmond.corp.microsoft.com>
> -----Original Message-----
> From: fantasai [mailto:fantasai.lists@inkedblade.net]
> Sent: Thursday, March 31, 2011 12:03 PM
> Explaining how line breaking works. How pagination works. How the borders
> and backgrounds are applied to the broken boxes. Etc. I don't have any
> specific instances off the top of my head, but I've run across the
> terminology issue multiple times when working on CSS2.1 text.
> In many cases using the term 'element', e.g. "block container element"
> doesn't work because we also have to consider anonymous boxes, which split
> into multiple boxes, but are still all part of one box.

Maybe it's OK for both kinds of boxes to just be boxes? They have the same nature. If "war and peace" is split into two volumes, each volume is a book, and "war and peace" is a book, too, isn't it?
Received on Thursday, 31 March 2011 19:23:35 UTC

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