fragmenter -> fragmentainer. Want a better term? Suggest one. :)

Author: fantasai

css3-break/Overview.html

@@ -178,7 +178,7 @@ <h2 class="no-num no-toc" id=contents> Table of contents</h2>
     Breaking</a>
     <ul class=toc>
      <li><a href="#varying-size-boxes"><span class=secno>5.1. </span>
-      Breaking into Varying-size Fragmenters</a>
+      Breaking into Varying-size Fragmentainers</a>
 
      <li><a href="#break-margins"><span class=secno>5.2. </span> Margins at
       Breaks</a>
@@ -245,9 +245,10 @@ <h2 id=intro><span class=secno>1. </span> Introduction</h2>
    href="#CSS3COL" rel=biblioentry>[CSS3COL]<!--{{CSS3COL}}--></a> create a
    similarly fragmented environment. The generic term for breaking content
    across containers is <dfn id=fragmentation>fragmentation</dfn>. This
-   module explains how content breaks across <i>fragmenters</i> such as pages
-   and columns and how such breaks can be <a
-   href="#breaking-controls">controlled by the author</a>.
+   module explains how content breaks across <a
+   href="#fragmentainer"><i>fragmentainers</i></a> such as pages and columns
+   and how such breaks can be <a href="#breaking-controls">controlled by the
+   author</a>.
 
   <h3 id=placement><span class=secno>1.1. </span> Module Interactions</h3>
 
@@ -289,20 +290,22 @@ <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
     chain of <a href="http://www.w3.org/TR/css3-regions">CSS regions</a>, or
     a <a href="http://www.w3.org/TR/css3-page/">paged media display</a>.
 
-   <dt><dfn id=fragmentation-container>fragmentation container</dfn>
+   <dt><dfn id=fragmentation-container>fragmentation container</dfn> (<dfn
+    id=fragmentainer>fragmentainer</dfn>)
 
    <dd> A box&mdash;such as a page box, column box, or region&mdash;that
     contains a portion (or all) of a <a href="#fragmented-flow"><i>fragmented
-    flow</i></a>. Fragmenters can be pre-defined, or generated as needed.
-    When breakable content overflows a fragmenter in the block dimension,
+    flow</i></a>. Fragmentainers can be pre-defined, or generated as needed.
+    When breakable content overflows a fragmentainer in the block dimension,
     instead of overflowing it breaks into the next container in its <a
     href="#fragmentation-context"><i>fragmentation context</i></a>.
 
    <dt><dfn id=fragmentation-context>fragmentation context</dfn>
 
-   <dd> An ordered series of <i>fragmenters</i>. A given fragmentation
+   <dd> An ordered series of <a
+    href="#fragmentainer"><i>fragmentainers</i></a>. A given fragmentation
     context can only have one block flow direction across all its
-    fragmenters.
+    fragmentainers.
 
    <dt><dfn id=fragmentation-direction>fragmentation direction</dfn>
 
@@ -311,37 +314,41 @@ <h2 id=fragmentation-model><span class=secno>2. </span> Fragmentation Model
 
    <dt><dfn id=fragmentation0>fragmentation</dfn>
 
-   <dd> The process of splitting a content flow across the <i>fragmenters</i>
-    that form a <a href="#fragmentation-context"><i>fragmentation
-    context</i></a>.
+   <dd> The process of splitting a content flow across the <a
+    href="#fragmentainer"><i>fragmentainers</i></a> that form a <a
+    href="#fragmentation-context"><i>fragmentation context</i></a>.
 
    <dt><dfn id=box-fragment>box fragment</dfn> or <dfn
     id=fragment>fragment</dfn>
 
-   <dd> The portion of a box that belongs to exactly one <i>fragmenter</i>. A
-    box in continuous flow always consists of only one fragment. A box in a
-    fragmented flow consists of one or more fragments.
+   <dd> The portion of a box that belongs to exactly one <a
+    href="#fragmentainer"><i>fragmentainer</i></a>. A box in continuous flow
+    always consists of only one fragment. A box in a fragmented flow consists
+    of one or more fragments.
 
-   <dt><dfn id=available-fragmenter-extent>available fragmenter extent</dfn>
+   <dt><dfn id=available-fragmentainer-extent>available fragmentainer
+    extent</dfn>
 
-   <dd> The remaining extent on the fragmenter available to a given element,
-    i.e. between the end of preceding content on fragmenter and the edge of
-    the fragmenter.
+   <dd> The remaining extent on the fragmentainer available to a given
+    element, i.e. between the end of preceding content on fragmentainer and
+    the edge of the fragmentainer.
   </dl>
 
   <p> Each <dfn id=fragmentation-break>fragmentation break</dfn> (hereafter,
    <dfn id=break>break</dfn>) ends layout of the fragmented box in the
-   current <i>fragmenter</i> and causes the remaining content to be laid out
-   in the next <i>fragmenter</i>, in some cases causing a new fragmenter to
-   be generated to hold the deferred content. When multiple flows are laid
-   out in parallel, fragmentation is performed independently in each flow.
-
-  <p> Breaking a fragmenter F effectively splits the fragmenter into two
-   fragmenters (F<sub>1</sub> and F<sub>2</sub>). The only difference is that
-   the type of break between the two pieces F<sub>1</sub> and F<sub>2</sub>
-   is the <a href="#break-types">type of break</a> created by the
-   fragmentation context that split F, not the type of break normally created
-   by F's own fragmentation context.
+   current <a href="#fragmentainer"><i>fragmentainer</i></a> and causes the
+   remaining content to be laid out in the next <a
+   href="#fragmentainer"><i>fragmentainer</i></a>, in some cases causing a
+   new fragmentainer to be generated to hold the deferred content. When
+   multiple flows are laid out in parallel, fragmentation is performed
+   independently in each flow.
+
+  <p> Breaking a fragmentainer F effectively splits the fragmentainer into
+   two fragmentainers (F<sub>1</sub> and F<sub>2</sub>). The only difference
+   is that the type of break between the two pieces F<sub>1</sub> and
+   F<sub>2</sub> is the <a href="#break-types">type of break</a> created by
+   the fragmentation context that split F, not the type of break normally
+   created by F's own fragmentation context.
 
   <p class=note> Breaking inline content into lines is another form of
    fragmentation, and similarly creates box fragments when it breaks <a
@@ -698,7 +705,7 @@ <h3 id=widows-orphans><span class=secno>3.2. </span> Breaks inside
 
   <h2 id=breaking-rules><span class=secno>4. </span> Rules for Breaking</h2>
 
-  <p> A fragmented flow may be broken across fragmenters at a number of <a
+  <p> A fragmented flow may be broken across fragmentainers at a number of <a
    href="#possible-breaks">possible break points</a>. In the case of <a
    href="#forced-breaks">forced breaks</a>, the UA is required to break the
    flow at that point. In the case of <a href="#unforced-breaks">unforced
@@ -756,11 +763,11 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
    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 fragmenter. In both
-   cases it must treat the element as having &lsquo;<code
+   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 fragmenter edge if there are no <a href="#possible-breaks">possible
-   break points</a> on the fragmenter.
+   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
    the page, and not all the content fits, the UA may break anywhere in order
@@ -769,7 +776,7 @@ <h3 id=possible-breaks><span class=secno>4.1. </span> Possible Break Points</h3>
   <h3 id=break-types><span class=secno>4.2. </span> Types of Breaks</h3>
 
   <p> There are different types of breaks in CSS, defined based on the type
-   of fragmenters they span:
+   of fragmentainers they span:
 
   <dl>
    <dt><dfn id=page-break>page break</dfn>
@@ -891,17 +898,17 @@ <h3 id=best-breaks><span class=secno>4.5. </span> Optimizing Unforced
    Breaks</h3>
 
   <p>While CSS3 requires that a fragmented flow must break at allowed break
-   points in order to avoid overflowing the fragmenters in its fragmentation
-   context, it does not define whether content breaks at a particular <a
-   href="#unforced-breaks">allowed break</a>. However, it is recommended that
-   user agents observe the following guidelines (while recognizing that they
-   are sometimes contradictory):
+   points in order to avoid overflowing the fragmentainers in its
+   fragmentation context, it does not define whether content breaks at a
+   particular <a href="#unforced-breaks">allowed break</a>. However, it is
+   recommended that user agents observe the following guidelines (while
+   recognizing that they are sometimes contradictory):
 
   <ul>
    <li>Break as few times as possible.
 
-   <li>Make all fragmenters that don't end with a forced break appear to be
-    equally filled with content.
+   <li>Make all fragmentainers that don't end with a forced break appear to
+    be equally filled with content.
 
    <li>Avoid breaking inside a replaced element.
   </ul>
@@ -955,34 +962,35 @@ <h2 id=breaking-boxes><span class=secno>5. </span> Box Model for Breaking</h2>
    rel=biblioentry>[CSS3-WRITING-MODES]<!--{{CSS3-WRITING-MODES}}--></a>.
 
   <h3 id=varying-size-boxes><span class=secno>5.1. </span> Breaking into
-   Varying-size Fragmenters</h3>
+   Varying-size Fragmentainers</h3>
 
-  <p> When a flow is fragmented into varying-size fragmenters, the following
-   rules are observed for adapting layout:
+  <p> When a flow is fragmented into varying-size fragmentainers, the
+   following rules are observed for adapting layout:
 
   <ul>
    <li> Intrinsic sizes are calculated and maintained across the entire
     element. Where an initial containing block size is needed to resolve an
-    intrinsic size, assume the size of the first fragmenter defining a
+    intrinsic size, assume the size of the first fragmentainer defining a
     pagination context.
 
-   <li> Layout is performed per-fragmenter, with each fragmenter continuing
-    progress from the breakpoint on the previous, but recalculating sizes and
-    positions using its own size as if the entire element were fragmented
-    across fragmenters of this size. Progress is measured in percentages (not
-    absolute lengths) of used/available fragmenter 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 fragmenters.
+   <li> Layout is performed per-fragmentainer, with each fragmentainer
+    continuing progress from the breakpoint on the previous, but
+    recalculating sizes and positions using its own size as if the entire
+    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
+    fragmentainers.
 
    <li><strong class=issue>Option A:</strong> Fragments of boxes that began
-    on a previous fragmenter must start at the top of the new fragmenter. If
-    this results in multiple boxes side-by-side that would otherwise be
-    staggered (if they were not continuations) in order to fit, the elements'
-    widths are reduced (on that fragmenter only) in proportion to their
-    original widths until they fit. However they are not reduced past their
-    min-content width or in case the width copmutes to a non-percent length
-    value.
+    on a previous fragmentainer must start at the top of the new
+    fragmentainer. If this results in multiple boxes side-by-side that would
+    otherwise be staggered (if they were not continuations) in order to fit,
+    the elements' widths are reduced (on that fragmentainer only) in
+    proportion to their original widths until they fit. However they are not
+    reduced past their min-content width or in case the width copmutes to a
+    non-percent length value.
     <div class=figure>
      <pre>First page
 <!--    -->+----------------------------------+
@@ -1024,11 +1032,11 @@ <h3 id=varying-size-boxes><span class=secno>5.1. </span> Breaking into
     </div>
 
    <li><strong class=issue>Option B:</strong> Fragments of boxes that began
-    on a previous fragmenter must obey placement rules with the additional
+    on a previous fragmentainer must obey placement rules with the additional
     constraint that fragments must not be positioned above the before edge of
-    the fragmenter and must otherwise be placed as high as possible while not
-    violating other constraints. If this results in a box's continuation
-    fragment shifting away from the before edge of the fragmenter, then
+    the fragmentainer and must otherwise be placed as high as possible while
+    not violating other constraints. If this results in a box's continuation
+    fragment shifting away from the before edge of the fragmentainer, then
     &lsquo;<code class=css>box-decoration-break: clone</code>&rsquo;, if
     specified, wraps the fragment with the box's margin in addition to its
     padding and border.
@@ -1149,10 +1157,10 @@ <h3 id=break-decoration><span class=secno>5.3. </span> Decorating Box
    where the split occurs. If they do not (i.e. &lsquo;<code
    class=css>slice</code>&rsquo; is specified), the box's background and side
    margins, border, and padding extend from the effective break point to the
-   end of the fragmenter (and across the ensuing blank fragmenter if one is
-   generated due to &lsquo;<code class=css>left</code>&rsquo; or &lsquo;<code
-   class=css>right</code>&rsquo; breaking). <span class=issue>Does this use
-   up height?</span>
+   end of the fragmentainer (and across the ensuing blank fragmentainer if
+   one is generated due to &lsquo;<code class=css>left</code>&rsquo; or
+   &lsquo;<code class=css>right</code>&rsquo; breaking). <span
+   class=issue>Does this use up height?</span>
 
   <h2 id=conformance><span class=secno>6. </span> Conformance</h2>
 
@@ -1449,8 +1457,9 @@ <h2 class=no-num id=index>Index</h2>
    <li>authoring tool, <a href="#authoring-tool"
     title="authoring tool"><strong>6.2.</strong></a>
 
-   <li>available fragmenter extent, <a href="#available-fragmenter-extent"
-    title="available fragmenter extent"><strong>2.</strong></a>
+   <li>available fragmentainer extent, <a
+    href="#available-fragmentainer-extent"
+    title="available fragmentainer extent"><strong>2.</strong></a>
 
    <li>avoid break values, <a href="#avoid-break-values"
     title="avoid break values"><strong>3.1.</strong></a>
@@ -1477,6 +1486,9 @@ <h2 class=no-num id=index>Index</h2>
 
    <li>fragment, <a href="#fragment" title=fragment><strong>2.</strong></a>
 
+   <li>fragmentainer, <a href="#fragmentainer"
+    title=fragmentainer><strong>2.</strong></a>
+
    <li>fragmentation, <a href="#fragmentation"
     title=fragmentation><strong>1.</strong></a>, <a href="#fragmentation0"
     title=fragmentation><strong>2.</strong></a>