Bugzilla – Bug 17138
Stricter use of box terminology throughout in spec (follow-up to Issue 120, inc Issue 266)
Last modified: 2012-12-04 00:54:12 UTC
This is a follow-up to Issue 120 (http://wiki.csswg.org/spec/css2.1#issue-120) consisting of Issue 266 together with other associated change proposals.
Reported by Anton Prowse
Need to tighten up the use of box terminology throughout the spec, in response to the terminology changes made in Issue 120. The changes are described in Issue 266:
Issue 266: http://wiki.csswg.org/spec/css2.1#issue-266
Issue 120 follow-up
* Accept proposals 1 & 2 with "block container element" instead of "block container"
accept 5 with s/which/that/
accept 7 (but beware second set of edits applies to second quoted sentence, not first)
Accept issue 6 edits, push rest to errata.
Reported by Kang-Hao (Kenny) Lu
9.5.1 ('float') says:
# The element generates a block box that is floated to the left.
# Content flows on the right side of the box, starting at the top
# (subject to the 'clear' property).
11.1.1 (Overflow: the 'overflow' property) says:
# This value indicates that content is not clipped, i.e., it may be
# rendered outside the block box.
since the box is not necessarily a block box (nor even a block container box; see Bug 15381), and the phrase "element's box" is used elsewhere in this section.
17.4 (Tables in the visual formatting model) says:
# In terms of the visual formatting model, a table can behave like a
# block-level (for 'display: table') or inline-level (for
# 'display: inline-table') element.
# In both cases, the table generates a principal block box called the table
# wrapper box
s/block box/block container box/
since the box is not necessarily block-level, as described in the first quoted paragraph.