[css-break] Transforms are applied independently to each fragment. <http://lists.w3.org/Archives/Public/www-style/2013Feb/0472.html> Also file Dirk's issue on overflow fragments.

--HG--
extra : rebase_source : a15cd290455b67c0d47fa8901f7469070f826e59

Author: fantasai

css-break/Overview.html

@@ -12,7 +12,7 @@
    rel=dcterms.rights>
   <meta content="CSS Fragmentation Module Level 3" name=dcterms.title>
   <meta content=text name=dcterms.type>
-  <meta content=2013-12-13 name=dcterms.date>
+  <meta content=2014-01-13 name=dcterms.date>
   <meta content="Rossen Atanassov" name=dcterms.creator>
   <meta content="Microsoft Corporation" name=dcterms.creator>
   <meta
@@ -34,11 +34,11 @@
    <h1 id=css-fragmentation-module>CSS Fragmentation Module Level 3:<br>
     Breaking the Web, one fragment at a time</h1>
 
-   <h2 class="no-num no-toc">Editor's Draft 13 December 2013</h2>
+   <h2 class="no-num no-toc">Editor's Draft 13 January 2014</h2>
 
    <dl>
     <dt>This version:</dt>
-    <!--<dd><a href="http://dev.w3.org/csswg/css3-break/">http://www.w3.org/TR/2013/WD-css3-break-20131213/</a></dd>-->
+    <!--<dd><a href="http://dev.w3.org/csswg/css3-break/">http://www.w3.org/TR/2014/WD-css3-break-20140113/</a></dd>-->
 
     <dd><a
      href="http://dev.w3.org/csswg/css3-break/">http://dev.w3.org/csswg/css3-break/</a>
@@ -87,7 +87,7 @@ <h2 class="no-num no-toc">Editor's Draft 13 December 2013</h2>
    <!--begin-copyright-->
    <p class=copyright><a
     href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright"
-    rel=license>Copyright</a> © 2013 <a href="http://www.w3.org/"><abbr
+    rel=license>Copyright</a> © 2014 <a href="http://www.w3.org/"><abbr
     title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a
     href="http://www.csail.mit.edu/"><abbr
     title="Massachusetts Institute of Technology">MIT</abbr></a>, <a
@@ -1485,10 +1485,17 @@ <h3 id=transforms><span class=secno>5.5. </span> Transforms, Positioning,
    rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>, transforms <a
    href="#ref-CSS3-TRANSFORMS"
    rel=biblioentry>[CSS3-TRANSFORMS]<!--{{!CSS3-TRANSFORMS}}--></a>, and any
-   other graphical effects. 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 rather than being clipped by its originating page.
+   other graphical effects. Such effects are applied per fragment: for
+   example, rotation applied to a fragmented box will calculate a rotation
+   origin for each fragment and independently rotate that fragment around its
+   origin. 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 rather than being
+   clipped by its originating page.
+
+  <p class=issue> There's an issue of how to handle fragments consisting
+   entirely of overflowing content. See <a
+   href="http://lists.w3.org/Archives/Public/www-style/2013Dec/0471.html">discussion</a>.
 
   <p> Absolute positioning affects layout and thus interacts with
    fragmentation. Both the coordinate system and absolutely-positioned boxes

css-break/Overview.src.html

@@ -1186,11 +1186,19 @@ <h3 id="transforms">
     Fragmentation interacts with layout, and thus occurs <em>before</em>
     relative positioning [[!CSS21]], transforms [[!CSS3-TRANSFORMS]],
     and any other graphical effects.
+    Such effects are applied per fragment:
+    for example, rotation applied to a fragmented box
+    will calculate a rotation origin for each fragment
+    and independently rotate that fragment around its origin.
     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
     rather than being clipped by its originating page.
 
+  <p class="issue">
+    There's an issue of how to handle fragments consisting entirely of overflowing content.
+    See <a href="http://lists.w3.org/Archives/Public/www-style/2013Dec/0471.html">discussion</a>.
+
   <p>
     Absolute positioning affects layout and thus interacts with fragmentation.
     Both the coordinate system and absolutely-positioned boxes belonging to a containing block