parent -> containing block <http://lists.w3.org/Archives/Public/www-style/2012Mar/0440.htm>

Author: fantasai

css3-break/Overview.html

@@ -548,7 +548,7 @@ <h3 id=break-properties><span class=secno>3.1. </span> Forced breaks and
   </dl>
 
   <p> A potential page/column/region break location is typically under the
-   influence of the parent element's &lsquo;<a href="#break-inside"><code
+   influence of the containing block's &lsquo;<a href="#break-inside"><code
    class=property>break-inside</code></a>&rsquo; property, the &lsquo;<a
    href="#break-after"><code class=property>break-after</code></a>&rsquo;
    property of the preceding element, and the &lsquo;<a
@@ -708,17 +708,17 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
 
    <dd> Between sibling boxes of the following types:
     <dl>
-     <dt>When the block flow direction of the siblings' parent is parallel to
-      that of the fragmentation context
+     <dt>Block-parallel Fragmentation
 
-     <dd> block-level boxes, table row group boxes, table row boxes,
-      multi-column column row boxes
+     <dd> When the block flow direction of the siblings' containing block is
+      parallel to that of the fragmentation context: block-level boxes, table
+      row group boxes, table row boxes, multi-column column row boxes
 
-     <dt>When the block flow direction of the siblings' parent is
-      perpendicular to that of the fragmentation context
+     <dt>Block-perpendicular Fragmentation
 
-     <dd> table column group boxes, table column boxes, multi-column column
-      boxes
+     <dd> When the block flow direction of the siblings' containing block is
+      perpendicular to that of the fragmentation context: table column group
+      boxes, table column boxes, multi-column column boxes
     </dl>
 
    <dt id=btw-lines>Class 2
@@ -736,12 +736,12 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
   <p class=note> Other layout models may add breakpoints to the above
    classes.
 
-  <p> Since breaks are only allowed between siblings (1), not between a child
-   and its parent, a &lsquo;<a href="#break-before"><code
+  <p> Since breaks are only allowed between siblings (1), not between a box
+   and its container, a &lsquo;<a href="#break-before"><code
    class=property>break-before</code></a>&rsquo; value on a first-child box
-   is propagated to its parent. Likewise a &lsquo;<a
+   is propagated to its container. Likewise a &lsquo;<a
    href="#break-after"><code class=property>break-after</code></a>&rsquo;
-   value on a last-child box is propagated to its parent.
+   value on a last-child box is propagated to its container.
 
   <p> When paginating, if there are no possible break points below the top of
    the page, and not all the content fits, the UA may break anywhere in order

css3-break/Overview.src.html

@@ -349,13 +349,16 @@ <h3 id="break-properties">
 
   <p>
     A potential page/column/region break location is typically under the influence of
-    the parent element's 'break-inside' property, the 'break-after' property of the
-    preceding element, and the 'break-before' property of the following element. When
-    these properties have values other than ''auto'', the <dfn>forced break values</dfn> (''always'',
-    ''left'', ''right'', ''page'', ''column'' and ''region'') take precedence over the
-    <dfn>avoid break values</dfn> (''avoid'', ''avoid-page'', ''avoid-column'' and ''avoid-region''). See the section
-    on <a href="#breaking-rules">rules for breaking</a> for the exact rules on how these
-    properties affect forced breaks.
+    the containing block's 'break-inside' property,
+    the 'break-after' property of the preceding element,
+    and the 'break-before' property of the following element.
+    When these properties have values other than ''auto'',
+    the <dfn>forced break values</dfn>
+    (''always'', ''left'', ''right'', ''page'', ''column'' and ''region'')
+    take precedence over the <dfn>avoid break values</dfn>
+    (''avoid'', ''avoid-page'', ''avoid-column'' and ''avoid-region'').
+    See the section on <a href="#breaking-rules">rules for breaking</a>
+    for the exact rules on how these properties affect forced breaks.
   </p>
   <p>
     User Agents must apply these properties to block-level boxes and to table rows,
@@ -482,15 +485,18 @@ <h3 id="possible-breaks">
     <dd>
       Between sibling boxes of the following types:
       <dl>
-        <dt>When the block flow direction of the siblings' parent is parallel
-        to that of the fragmentation context</dt>
+        <dt>Block-parallel Fragmentation</dt>
         <dd>
-          block-level boxes, table row group boxes, table row boxes, multi-column
-          column row boxes
+          When the block flow direction of the siblings' containing block
+          is parallel to that of the fragmentation context:
+          block-level boxes, table row group boxes, table row boxes,
+          multi-column column row boxes
         </dd>
-        <dt>When the block flow direction of the siblings' parent is perpendicular
-        to that of the fragmentation context</dt>
+        <dt>Block-perpendicular Fragmentation</dt>
         <dd>
+          When the block flow direction of the siblings' containing block
+          is perpendicular
+          to that of the fragmentation context:
           table column group boxes, table column boxes, multi-column column boxes
         </dd>
     </dl>
@@ -512,10 +518,10 @@ <h3 id="possible-breaks">
   </p>
 
   <p>
-    Since breaks are only allowed between siblings (1), not between
-    a child and its parent, a 'break-before' value on a first-child box is
-    propagated to its parent. Likewise a 'break-after' value on a last-child
-    box is propagated to its parent.
+    Since breaks are only allowed between siblings (1),
+    not between a box and its container,
+    a 'break-before' value on a first-child box is propagated to its container.
+    Likewise a 'break-after' value on a last-child box is propagated to its container.
   </p>
   <p>
     When paginating, if there are no possible break points below the top