[Bug 17121] Need to introduce the concept of a "formatting context" for forwards compatibility

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17121

--- Comment #2 from Anton P <antonsforums@yahoo.co.uk> 2012-05-20 14:43:22 UTC ---
Issue reported by Morten Stenshorne

Conversation begins:
Bug description:
http://lists.w3.org/Archives/Public/www-style/2012May/0438.html

Proposal A: http://lists.w3.org/Archives/Public/www-style/2012May/0494.html

In 9.4 (Normal flow), replace:

   # Boxes in the normal flow belong to a formatting context, which may
   # be block or inline, but not both simultaneously. Block-level boxes
   # participate in a block formatting context. Inline-level boxes
   # participate in an inline formatting context.

with:

   | Boxes in the normal flow belong to a formatting context, which in
   | CSS21 may be block, inline or table. In future levels of CSS, other
   | types of formatting context will be introduced. Block-level boxes
   | participate in a block formatting context. Inline-level boxes
   | participate in an inline formatting context. Table formatting
   | contexts are described in the chapter on _tables_.

In 17.4 (Tables in the visual formatting model), replace:

   # [...] The table wrapper box establishes a block formatting context.
   # [...]

with:

   # [...] The table wrapper box establishes a block formatting context,
   # and the table box establishes a table formatting context. [...]

In 17.5 (Visual layout of table contents), replace:

   # Internal table elements generate rectangular boxes with content and
   # borders. Cells have padding as well. Internal table elements do not
   # have margins.

with:

   # Internal table elements generate rectangular boxes which
   # participate in the table formatting context established by the
   # table box. These boxes have content and borders, and cells have
   # padding as well. Internal table elements do not have margins.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Sunday, 20 May 2012 14:43:26 UTC