- From: Elika Etemad via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 31 Mar 2011 20:54:08 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-writing-modes
In directory hutz:/tmp/cvs-serv15812
Modified Files:
Overview.html Overview.src.html
Log Message:
Revise orthogonal flows with multicol section.
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.html,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -d -r1.91 -r1.92
--- Overview.html 31 Mar 2011 20:25:37 -0000 1.91
+++ Overview.html 31 Mar 2011 20:54:05 -0000 1.92
@@ -2261,28 +2261,45 @@
the available extent is defined but the available measure is infinite and
the element's measure is unconstrained (is not fixed and has no maximum):
- <ul>
+ <ol>
<li>If ‘<code class=property>column-count</code>’ and
‘<code class=property>column-width</code>’ are both ‘<a
href="#auto"><code class=css>auto</code></a>’, then the
‘<code class=property>column-count</code>’ is assumed to be
‘<code class=css>1</code>’, and the following rules apply.
- <li>If the ‘<code class=property>column-count</code>’ is not
+ <li>If the ‘<code class=property>column-width</code>’ is
‘<a href="#auto"><code class=css>auto</code></a>’, the column
width is calculated as if the element's containing block were the initial
- containing block, and the rest of the layout is calculated as described
- below for non-‘<a href="#auto"><code
- class=css>auto</code></a>’ column widths.
+ containing block.
- <li>If the ‘<code class=property>column-width</code>’ is not
- ‘<a href="#auto"><code class=css>auto</code></a>’, the
- available extent is used to calculate the column extent by subtracting
- out the element's margins, borders, and padding in the block dimension
- and flooring the result at zero. The used column-count and the used
- measure of the element then follow from filling the resulting columns
+ <li>If the column's extent is not defined, the available extent is used to
+ calculate the column extent by subtracting out the element's margins,
+ borders, and padding in the block dimension and flooring the result at
+ zero.
+
+ <li>The used column-count then follows from filling the resulting columns
with the element's content.
- </ul>
+ </ol>
+
+ <p>The used measure of the element is then the ‘<code
+ class=css>max-content</code>’ measure of the resulting multi-column
+ element. (If the content neither wraps nor paginates within the
+ multi-column element, then this will be the intrinsic measure of the
+ content; else it will be calculated from the used column width, column
+ count, and column gap.)
+
+ <p>The used extent of the element is either the used column extent (if
+ multiple columns were used) or the intrinsic extent of the content.
+
+ <p class=issue>Does CSS3 Multi-col define shrink-wrap sizing? Because
+ that's what we're trying to use here in the last two steps...
+
+ <p class=note>This should behave the same as the auto-sizing algorithm
+ defined in the previous section, except overflowing content, instead of
+ continuing off the side of the containing block, is wrapped into columns
+ in the flow direction of the containing block, thus avoiding T-shaped
+ documents.
<h4 id=orthogonal-pagination><span class=secno>7.3.3. </span> Paginating
Orthogonal Flows</h4>
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-writing-modes/Overview.src.html,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -d -r1.95 -r1.96
--- Overview.src.html 31 Mar 2011 20:25:37 -0000 1.95
+++ Overview.src.html 31 Mar 2011 20:54:05 -0000 1.96
@@ -1672,21 +1672,38 @@
available measure is infinite and the element's measure is
unconstrained (is not fixed and has no maximum):
- <ul>
+ <ol>
<li>If 'column-count' and 'column-width' are both ''auto'', then
the 'column-count' is assumed to be ''1'', and the following rules
apply.
- <li>If the 'column-count' is not ''auto'', the column width is
+ <li>If the 'column-width' is ''auto'', the column width is
calculated as if the element's containing block were the initial
- containing block, and the rest of the layout is calculated as
- described below for non-''auto'' column widths.
- <li>If the 'column-width' is not ''auto'', the available extent is
+ containing block.
+ <li>If the column's extent is not defined, the available extent is
used to calculate the column extent by subtracting out the element's
margins, borders, and padding in the block dimension and flooring
- the result at zero. The used column-count and the used measure of
- the element then follow from filling the resulting columns with the
- element's content.
- </ul>
+ the result at zero.
+ <li>The used column-count then follows from filling the resulting
+ columns with the element's content.
+ </ol>
+
+ <p>The used measure of the element is then the ''max-content'' measure
+ of the resulting multi-column element.
+ (If the content neither wraps nor paginates within the multi-column
+ element, then this will be the intrinsic measure of the content;
+ else it will be calculated from the used column width, column count,
+ and column gap.)
+ <p>The used extent of the element is either the used column extent
+ (if multiple columns were used) or the intrinsic extent of the content.
+
+ <p class="issue">Does CSS3 Multi-col define shrink-wrap sizing? Because
+ that's what we're trying to use here in the last two steps...</p>
+
+ <p class="note">This should behave the same as the auto-sizing algorithm
+ defined in the previous section, except overflowing content, instead of
+ continuing off the side of the containing block, is wrapped into
+ columns in the flow direction of the containing block, thus avoiding
+ T-shaped documents.</p>
<h4 id="orthogonal-pagination">
Paginating Orthogonal Flows</h4>
Received on Thursday, 31 March 2011 20:54:09 UTC