csswg/css3-gcpm Overview.html,1.127,1.128

Update of /sources/public/csswg/css3-gcpm
In directory hutz:/tmp/cvs-serv9981

Modified Files:
	Overview.html 
Log Message:
x

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-gcpm/Overview.html,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -d -r1.127 -r1.128
--- Overview.html	9 Oct 2011 15:48:28 -0000	1.127
+++ Overview.html	9 Oct 2011 16:59:48 -0000	1.128
@@ -3203,17 +3203,17 @@
     class=property>float-modifier</code>&rsquo;, provides support for common
     paper-based layouts.
 
-   <p>(A few words about the difference between mk2 and mk1: Care has now
-    been taken to avoid layouts that are hard to achieve, or that can be
-    achieved in other ways. For example, by saying &lsquo;<code
-    class=property>top-corner</code>&rsquo; instead of &lsquo;<code
-    class=css>top left</code>&rsquo; or &lsquo;<code class=css>top
-    right</code>&rsquo;, it becomes impossible to specify a layout where one
-    has to replace already laid-out content. Compared to the mk1 float model,
-    mk2 does not allow one to explicityly set the containing block of the
-    float; the CB is the column or the multicol element (depending on which
-    keyword in use). It is therefore impossible to float something to the top
-    of the page. However, given that &lsquo;<code
+   <p>(A few words about the difference between this proposa, and the one
+    sketched in the next section: Care has now been taken to avoid layouts
+    that are hard to achieve, or that can be achieved in other ways. For
+    example, by saying &lsquo;<code class=property>top-corner</code>&rsquo;
+    instead of &lsquo;<code class=css>top left</code>&rsquo; or &lsquo;<code
+    class=css>top right</code>&rsquo;, it becomes impossible to specify a
+    layout where one has to replace already laid-out content. Compared to the
+    mk1 float model, mk2 does not allow one to explicityly set the containing
+    block of the float; the CB is the column or the multicol element
+    (depending on which keyword in use). It is therefore impossible to float
+    something to the top of the page. However, given that &lsquo;<code
     class=property>column-span</code>&rsquo; now is widely supported, a
     different strategy can be used: make the root element a multicol element,
     and float the box to the top. Thereby it ends up at the top of hte page.)
@@ -3233,9 +3233,8 @@
 
     <dt>top-corner
 
-    <dd>the box is floated to the top of the last column in the inline
-     direction that fits inside the multicol element on the same page. I.e.,
-     overflow columns are not considered.
+    <dd>the box is floated to the top of the last column (in the inline
+     direction) that fits inside the multicol element on the same page.
 
     <dt>bottom-corner
 
@@ -3253,27 +3252,36 @@
      determine if the box is near the top/bottom.
    </dl>
 
+   <p>These new keywords only apply in paged media; in continous media
+    declarations with these keywords are ignored.
+
    <div class=example>
-    <p>Float figure to top of natural column, being as wide as the column:
+    <p>Float figure to top of natural column:
 
     <pre>
-.figure { float: top; width: 100% }
+.figure { float: top }
 </pre>
     <img src=7.png></div>
 
+   <div class=example>
+    <pre>
+.figure { float: top; width: 50% }
+</pre>
+    <img src=7b.png></div>
+
    <div class=example> Float figure to top of the natural column, spanning
     all columns:
     <pre>
-.figure { float: top; column-span: all; width: 100% }
+.figure { float: top; column-span: all }
 </pre>
    </div>
 
    <div class=example>
     <p>Float figure to top/bottom of the last column of the multicol element
-     on that page, being as wide as the column:
+     on that page:
 
     <pre>
-.figure { float: top-corner; width: 100% }
+.figure { float: top-corner }
 </pre>
     <img src=6.png></div>

Received on Sunday, 9 October 2011 16:59:52 UTC