Define 'monolithic' elements, and define handling of 'overflow: hidden'.

Author: fantasai

css3-break/Overview.html

@@ -712,6 +712,20 @@ <h2 id=breaking-rules><span class=secno>4. </span> Rules for Breaking</h2>
    breaks</a> the UA has to choose among the possible breaks that are
    allowed.
 
+  <p> Some content is not fragmentable, for example many types of <a
+   href="">replaced elements</a> (such as images or video), scrollable
+   elements, or a single line of text content. Such content is considered
+   <dfn id=monolithic>monolithic</dfn>: it contains no possible break points.
+   In addition to any content which is not fragmentable, UAs may consider as
+   <a href="#monolithic"><i>monolithic</i></a> any elements with &lsquo;<code
+   class=property>overflow</code>&rsquo; set to &lsquo;<code
+   class=css>auto</code>&rsquo; or &lsquo;<code
+   class=css>scroll</code>&rsquo; and any elements with &lsquo;<code
+   class=css>overflow: hidden</code>&rsquo; and a non-&lsquo;<code
+   class=css>auto</code>&rsquo; <a
+   href="http://www.w3.org/TR/css3-writing-modes/#extent">logical height</a>
+   (and no specified maximum logical height).
+
   <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
 
   <p> Fragmentation splits boxes in the block flow dimension. In
@@ -757,16 +771,13 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
    href="#break-after"><code class=property>break-after</code></a>&rsquo;
    value on a last-child box is propagated to its container.
 
-  <p id=monolithic> The UA is not required to fragment the contents of
-   replaced or scrollable elements (e.g. those with &lsquo;<code
-   class=property>overflow</code>&rsquo; set to &lsquo;<code
-   class=css>auto</code>&rsquo; or &lsquo;<code
-   class=css>scroll</code>&rsquo;), and may instead either slice the
-   element's graphical representation as necessary to fragment it or treat
-   its box as monolithic (unbreakable) and overflow the fragmentainer. In
-   both cases it must treat the element as having &lsquo;<code
-   class=css>break-inside: avoid</code>&rsquo;, i.e. only slice or overflow
-   at the fragmentainer edge if there are no <a
+  <p id=monolithic-breaking> The UA is not required to fragment the contents
+   of <a href="#monolithic"><i>monolithic</i></a> elements, and may instead
+   either slice the element's graphical representation as necessary to
+   fragment it or treat its box as unbreakable and overflow the
+   fragmentainer. In both cases it must treat the element as having
+   &lsquo;<code class=css>break-inside: avoid</code>&rsquo;, i.e. only slice
+   or overflow at the fragmentainer edge if there are no <a
    href="#possible-breaks">possible break points</a> on the fragmentainer.
 
   <p> When paginating, if there are no possible break points below the top of
@@ -979,8 +990,8 @@ <h3 id=varying-size-boxes><span class=secno>5.1. </span> Breaking into
     element were fragmented across fragmentainers of this size. Progress is
     measured in percentages (not absolute lengths) of used/available
     fragmentainer extent and in amount of used/remaining content. However,
-    when laying out scrollable elements and certain replaced elements the UA
-    may instead maintain a consistent measure and resolved extent across
+    when laying out <a href="#monolithic"><i>monolithic</i></a> elements, the
+    UA may instead maintain a consistent measure and resolved extent across
     fragmentainers.
 
    <li><strong class=issue>Option A:</strong> Fragments of boxes that began
@@ -1511,6 +1522,9 @@ <h2 class=no-num id=index>Index</h2>
    <li>line break, <a href="#line-break"
     title="line break"><strong>4.2.</strong></a>
 
+   <li>monolithic, <a href="#monolithic"
+    title=monolithic><strong>4.</strong></a>
+
    <li>orphans, <a href="#orphans" title=orphans><strong>3.2.</strong></a>
 
    <li>page break, <a href="#page-break"

css3-break/Overview.src.html

@@ -483,6 +483,19 @@ <h2 id="breaking-rules">
     among the possible breaks that are allowed.
   </p>
 
+  <p>
+    Some content is not fragmentable, for example many types of
+    <a href="">replaced elements</a> (such as images or video),
+    scrollable elements, or a single line of text content.
+    Such content is considered <dfn>monolithic</dfn>:
+    it contains no possible break points.
+    In addition to any content which is not fragmentable,
+    UAs may consider as <i>monolithic</i> any elements with
+    'overflow' set to ''auto'' or ''scroll'' and
+    any elements with ''overflow: hidden'' and a non-''auto''
+    <a href="http://www.w3.org/TR/css3-writing-modes/#extent">logical height</a>
+    (and no specified maximum logical height).
+
 <h3 id="possible-breaks">
 Possible Break Points</h3>
 
@@ -533,11 +546,11 @@ <h3 id="possible-breaks">
     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 id=monolithic>
-    The UA is not required to fragment the contents of replaced or scrollable elements
-    (e.g. those with 'overflow' set to ''auto'' or ''scroll''), and may instead
-    either slice the element's graphical representation as necessary to fragment it
-    or treat its box as monolithic (unbreakable) and overflow the fragmentainer.
+  <p id=monolithic-breaking>
+    The UA is not required to fragment the contents of <i>monolithic</i> elements,
+    and may instead either slice the element's graphical representation
+    as necessary to fragment it
+    or treat its box as unbreakable and overflow the fragmentainer.
     In both cases it must treat the element as having ''break-inside: avoid'',
     i.e. only slice or overflow at the fragmentainer edge
     if there are no <a href="#possible-breaks">possible break points</a>
@@ -751,9 +764,9 @@ <h3 id="varying-size-boxes">
       across fragmentainers of this size. Progress is measured in percentages
       (not absolute lengths) of used/available fragmentainer extent and in amount of
       used/remaining content.
-      However, when laying out scrollable elements and certain replaced
-      elements the UA may instead maintain a consistent measure and resolved
-      extent across fragmentainers.
+      However, when laying out <i>monolithic</i> elements,
+      the UA may instead maintain a consistent measure and resolved extent
+      across fragmentainers.
     </li>
     <li><strong class="issue">Option A:</strong>
       Fragments of boxes that began on a previous fragmentainer must start at