[css=break] Addressed the open issue of transformed overflow content.

--HG--
extra : rebase_source : c5f18f250acafe2c1bb01de4909fb80c6f398b71

Author: Rossen Atanassov

css-break/Overview.src.html

@@ -35,8 +35,8 @@ <h2 class="no-num no-toc">[LONGSTATUS] [DATE]</h2>
 
   <dt>Feedback:</dt>
     <dd><a href="mailto:www-style@w3.org?subject=%5Bcss-break%5D%20feedback"
-         >www-style@w3.org</a> 
-         with subject line &ldquo;<kbd>[css-break] 
+         >www-style@w3.org</a>
+         with subject line &ldquo;<kbd>[css-break]
          <var>&hellip; message topic &hellip;</var></kbd>&rdquo;
          (<a rel="discussion" href="http://lists.w3.org/Archives/Public/www-style/"
            >archives</a>)
@@ -50,7 +50,7 @@ <h2 class="no-num no-toc" id="abstract">
 Abstract</h2>
 
   <p>
-    This module describes the fragmentation model that partitions a flow 
+    This module describes the fragmentation model that partitions a flow
     into pages, columns, or regions.
     It builds on the Page model module and introduces and defines the fragmentation
     model. It adds functionality for pagination, breaking variable fragment size and
@@ -249,7 +249,7 @@ <h2 id="breaking-controls">
     the 'break-after' property of the preceding element,
     and the 'break-before' property of the following element.
     A page/column/region break opportunity between line boxes
-    is under the influence of 
+    is under the influence of
     the containing block's 'break-inside', 'widows', and 'orphans' properties.
     A fragmentation break can be
     allowed, forced, or discouraged depending on the values of these properties.
@@ -333,11 +333,11 @@ <h4 class="no-num">
     <dt>''auto''
     <dd>
       Neither force nor forbid a break before/after the <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">principal box</a>.
-    </dd> 
+    </dd>
     <dt>''avoid''
     <dd>
       Avoid a break before/after the <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">principal box</a>.
-    </dd> 
+    </dd>
     <dt>''always''
     <dd>
       Always force a break
@@ -399,7 +399,7 @@ <h4 class="no-num">
   <dl>
     <dt>''avoid-column''
     <dd>
-      Avoid a column break before/after the <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">principal box</a>. 
+      Avoid a column break before/after the <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">principal box</a>.
     </dd>
     <dt>''column''
     <dd>
@@ -465,18 +465,18 @@ <h3 id="break-within">
     <dt>''auto''
     <dd>
       Impose no additional breaking constraints within the box.
-    </dd> 
+    </dd>
     <dt>''avoid''
     <dd>
       Avoid breaks within the box.
     </dd>
     <dt>''avoid-page''
     <dd>
-      Avoid a page break within the box. 
+      Avoid a page break within the box.
     </dd>
     <dt>''avoid-column''
     <dd>
-      Avoid a column break within the box. 
+      Avoid a column break within the box.
     </dd>
     <dt>''avoid-region''
     <dd>
@@ -550,7 +550,7 @@ <h3 id="page-break-properties">
   to 'break-before', 'break-after', and 'break-inside'
   by treating the 'page-break-*' properties as shorthands for the 'break-*' properties
   with the following value mappings:
-  
+
   <table class="data">
     <thead>
       <tr><th>Shorthand ('page-break-*') Values
@@ -592,7 +592,7 @@ <h2 id="breaking-rules">
   <p>
 	To guarantee progress, fragmentainers are assumend to have a minimum
 	extent of 1px regardless of their used size.
-	
+
 <h3 id="possible-breaks">
 Possible Break Points</h3>
 
@@ -873,7 +873,7 @@ <h3 id="varying-size-boxes">
   <ul>
     <li>
       Intrinsic sizes are calculated and maintained across the entire element.
-      Where an initial containing block size is needed to resolve an intrinsic 
+      Where an initial containing block size is needed to resolve an intrinsic
       size, assume the size of the first fragmentainer defining a fragmentation context.
     </li>
     <li>
@@ -930,7 +930,7 @@ <h3 id="varying-size-boxes">
   <p class="note">
     Since document order of elements doesn't change during fragmentation,
     fragments are processed following the same rules that apply to continuous
-    media. In particular, the order of floats is preserved across all 
+    media. In particular, the order of floats is preserved across all
     fragments and follows the same rules as defined in CSS 2.1 9.5.
   </p>
 
@@ -980,7 +980,7 @@ <h3 id="varying-size-boxes">
       moves to the second page, recording progress of 400/630 = 63.49% with
       36.51% left to go.
       <li>Now on the second page, the top position is again resolved, this
-      time against the height of the second page. This results in 330px. The 
+      time against the height of the second page. This results in 330px. The
       remaining 36.51% of progress thus resolves to 120.5px, placing the top edge of
       the element 120.5px down the second page.
       <li>Now the height is resolved against the second page; it resolves
@@ -1115,7 +1115,7 @@ <h3 id="break-decoration">
       (1) a single box cut in two in between two lines of text by a page break and
       (2) two boxes, one before and one after the page break,
       both with a border all around and their own background image" src="box-break.png">
-  
+
     <p class=caption>Two possibilities for 'box-decoration-break':
     on the left, the value ''slice'', on the right the value ''clone''.
   </div>
@@ -1203,6 +1203,8 @@ <h3 id="transforms">
     for example, rotation applied to a fragmented box
     will calculate a rotation origin for each fragment
     and independently rotate that fragment around its origin.
+    (The origin of an overflow-only fragment is determined
+    as if that content were overflowing an empty box with zero margins/borders/padding at the start of the fragmentainer.)
     However, the separation and transfer of page boxes <em>should</em> occur last;
     thus a transformed fragment that spans pages <em>should</em>
     be sliced at the page breaks and print in its entirety
@@ -1288,7 +1290,7 @@ <h3 id="conformance-classes">Conformance Classes</h3>
     individual grammars of each feature in this module, and meet all other conformance
     requirements of style sheets as described in this module.
   </p>
-  
+
 <h3 id="partial">
 Partial Implementations</h3>
 
@@ -1340,7 +1342,7 @@ <h3 id="testing">
         http://www.w3.org/Style/CSS/Test/</a>. Questions should be directed to the <a href="http://lists.w3.org/Archives/Public/public-css-testsuite">
             public-css-testsuite@w3.org</a> mailing list.
   </p>
-  
+
 <h3 id="cr-exit-criteria">
 CR Exit Criteria</h3>