15882 2012-02-04 15:33:26 +0000 Proposed editorial simplification to description of block formatting contexts in 9.4.1 (Issue 263) 2012-12-04 00:53:51 +0000 1 1 1 Unclassified CSS CSS Level 2 unspecified All Windows 3.1 NEW P2 normal --- 1 antonsforums bert public-css-bugzilla oldest_to_newest 63681 0 antonsforums 2012-02-04 15:33:26 +0000 Reported by Anton Prowse This is Issue 263 (see below). 9.4.1 (Block formatting contexts) says: # Floats, absolutely positioned elements, block containers (such as # inline-blocks, table-cells, and table-captions) that are not block # boxes, and block boxes with 'overflow' other than 'visible' (except # when that value has been propagated to the viewport) establish new # block formatting contexts. and 11.1.1 (Overflow: the 'overflow' property) says: # UAs must apply the 'overflow' property set on the root element to # the viewport. When the root element is an HTML "HTML" element or an # XHTML "html" element, and that element has an HTML "BODY" element # or an XHTML "body" element as a child, user agents must instead # apply the 'overflow' property from the first such child element to # the viewport, if the value on the root element is 'visible'. The # 'visible' value when used for the viewport must be interpreted as # 'auto'. The element from which the value is propagated must have a # used value for 'overflow' of 'visible'. So in fact if a block box whose 'overflow' other than 'visible' has been propagated to the viewport then its used value is 'visible' and so it's no longer under consideration is 9.4.1. In other words, 9.4.1 can be clarified as follows: s/block boxes with 'overflow' other than 'visible' (except when that value has been propagated to the viewport)/block boxes with used value of 'overflow' other than 'visible'/ This proposed change from (presumably) computed value to used value in 9.4.1 shouldn't cause any implementation difficulties because for all block boxes whose 'overflow' isn't propagated, the used value can only be other than visible if the computed value is also other than visible. Hence under the proposed change, it's known whether the block box establishes a BFC as soon as the computed value is calculated, just as it is with the current spec. I find 9.4.1 much easier to parse under this proposed change. Conversation begins: http://lists.w3.org/Archives/Public/www-style/2011Jan/0077.html Issue 263: http://wiki.csswg.org/spec/css2.1#issue-263 Summary Editorial simplification to 9.4.1 BFC root definition URL http://lists.w3.org/Archives/Public/www-style/2011Jan/0077.html Resolution Assumed editorial. Status Open. =errata= Deferred to Errata 63683 1 antonsforums 2012-02-04 16:09:13 +0000 Related bug: Bug 15702