csswg/css3-gcpm Overview.src.html,1.132,1.133

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

Modified Files:
	Overview.src.html 
Log Message:
revising img, adding example

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-gcpm/Overview.src.html,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -d -r1.132 -r1.133
--- Overview.src.html	9 Oct 2011 15:48:21 -0000	1.132
+++ Overview.src.html	9 Oct 2011 16:59:40 -0000	1.133
@@ -2600,18 +2600,19 @@
 and the new 'float-modifier', 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 'top-corner' instead of
-'top left' or 'top right', 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
-'column-span' 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.)
+<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 'top-corner' instead of 'top left' or 'top right',
+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 'column-span' 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.)
 
 <p>Four new keywords on 'float' have been added:
 
@@ -2624,7 +2625,7 @@
 <dd>the box is floated to the bottom of the natural column
 
 <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
 <dd>similar to 'top-corner', exept the box is floated to the bottom
@@ -2633,34 +2634,53 @@
 <dd>same as 'top' if the box is naturally near the top; same as 'bottom' if the box is naturally near the bottom. The 'widows'/'orphans' properties may be consulted to 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:
+<p>Float figure to top/bottom of the last column of the multicol element on that page:
 <pre>
-.figure { float: top-corner; width: 100% }
+.figure { float: top-corner }
 </pre>
 
 <img src=6.png>
 </div>
 
+
+
+
 <p class=issue>
 In the examples above, the width is set to 100% to fill the available space. This is typically how paper-based layouts have used column-span. If, however, the width is smaller than the available space, how should the box be positioned. (Probably on the side, based on the writing direction.) And, should content flow around it? (Probably not: it may be hard to implement and have little use.)
 </div>

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