- From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 23 Aug 2011 23:24:32 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv20185
Modified Files:
Overview.html Overview.src.html
Log Message:
Completed Action items L-8, L-11, L-12, L-13, L-14 and L-16. Updated change log
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- Overview.html 12 Aug 2011 00:13:51 -0000 1.16
+++ Overview.html 23 Aug 2011 23:24:30 -0000 1.17
@@ -25,13 +25,13 @@
<h1 id=css-regions-module>CSS regions Module</h1>
- <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 12 August 2011</h2>
+ <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 23 August 2011</h2>
<dl>
<dt>This version:
<dd><a
- href="http://www.w3.org/TR/2011/ED-css3-regions-20110812/">http://www.w3.org/csswg/css3-regions</a>
+ href="http://www.w3.org/TR/2011/ED-css3-regions-20110823/">http://www.w3.org/csswg/css3-regions</a>
<dt>Latest version:
@@ -187,13 +187,12 @@
<li><a href="#the-content-property"><span class=secno>3.2. </span>The
‘<code class=property>content</code>’ property</a>
- <li><a href="#the-content-order-property"><span class=secno>3.3.
- </span>The ‘<code class=property>content-order</code>’
+ <li><a href="#the-region-order-property"><span class=secno>3.3.
+ </span>The ‘<code class=property>region-order</code>’
property</a>
- <li><a
- href="#region-flow-break-properties-break-before-break-after-break-inside"><span
- class=secno>3.4. </span>Region flow break properties: ‘<code
+ <li><a href="#region-flow-break"><span class=secno>3.4. </span>Region
+ flow break properties: ‘<code
class=property>break-before</code>’, ‘<code
class=property>break-after</code>’, ‘<code
class=property>break-inside</code>’</a>
@@ -438,6 +437,8 @@
<h2 id=css-regions-concepts><span class=secno>2. </span>CSS regions
concepts</h2>
+ <p><em>This section is non-normative.</em>
+
<h3 id=regions><span class=secno>2.1. </span>Regions</h3>
<p class=index id=region title=region>A region is an element that generates
@@ -467,7 +468,7 @@
<p>Elements are placed into a named flow with the ’flow-into'
property. The elements in a named flow are laid out in the chain of
regions that are associated with this named flow. The ‘<a
- href="#content-order"><code class=property>content-order</code></a>’
+ href="#region-order"><code class=property>region-order</code></a>’
property defines how <span title=region>regions</span> are organized in to
a <span title=region-chain>region chain</span>.
@@ -532,7 +533,7 @@
<p><span title=region>Regions</span> are organized in to a <span
title=region-chain>region chain</span> (see the ‘<a
- href="#content-order"><code class=property>content-order</code></a>’
+ href="#region-order"><code class=property>region-order</code></a>’
property).
<p>Each region in turn consumes content from its associated <span
@@ -631,7 +632,7 @@
<p>The main CSS regions module properties are the ‘flow-into’ and 'content'
properties. The ‘flow-into’ property may place an element into a specific named
flow. The ‘content’ property binds a region with a particular named flow. When multiple
- regions are bound to the same flow, the 'content-order' property determines
+ regions are bound to the same flow, the 'region-order' property determines
the order in which content flows into the sequence of regions. This
sequences of regions is called a <dfn>region chain</dfn>.</p>
@@ -941,30 +942,26 @@
class=property>normal</code>’. <br>
Otherwise, the element becomes a <span>region</span> and is ordered in a
<span>region chain</span> according to its document order and ‘<a
- href="#content-order"><code
- class=property>content-order</code></a>’ property. The content from
- the flow with the <a
+ href="#region-order"><code class=property>region-order</code></a>’
+ property. The content from the flow with the <a
href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
- name will be <a
- href="#region-flow-break-properties-break-before-break-after-break-inside">broken
- into segments</a> and visually formatted in the <a
+ name will be <a href="#region-flow-break">broken into segments</a> and
+ visually formatted in the <a
href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal
boxes</a> of the regions in the region chain. If there is no flow with
name <ident>, then the element does not format any content
visually. <br>
+ Likewise, if the element is part of the flow with name <ident>,
+ then the element does not format any content visually. <br>
This might be expanded in future versions of the specification to allow
other types of containers to receive flow content.
</dl>
<p>When the ‘<a href="#content-from"><code
- class=property>content</code></a>’ property is set to ‘<code
- class=property>none</code>’, ‘<code
- class=property>from-flow</code>’, <string>, <uri>,
- <counter>, ‘<code
- class=css>attr(<identifier>)</code>’, open-quote, close-quote,
- no-open-quote or no-close-quote, the document children of the element are
- not visually formatted unless they are directed to a named flow referenced
- by one or more regions.
+ class=property>content</code></a>’ property is set to a value other
+ than ‘<code class=property>normal</code>’, the element's
+ document children are not visually formatted unless they are directed to a
+ named flow referenced by one or more regions.
<div class=note>
<p><em>This note is informative.</em></p>
@@ -1073,6 +1070,10 @@
<p><span title=region>Regions</span> create a new stacking context.
+ <p><span title=region>Regions</span> establish a new <a
+ href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block
+ formatting Context</a>.
+
<div class=note>
<p><em>This note is informative.</em></p>
@@ -1122,22 +1123,22 @@
</pre>
</div>
- <h3 id=the-content-order-property><span class=secno>3.3. </span>The
- ‘<a href="#content-order"><code
- class=property>content-order</code></a>’ property</h3>
+ <h3 id=the-region-order-property><span class=secno>3.3. </span>The
+ ‘<a href="#region-order"><code
+ class=property>region-order</code></a>’ property</h3>
<p>Defines the ordering of the chain of regions into which content flows.
If region A and region B are in the same chain of regions and the
- ‘content-order’ of region A is lower than that of region B, then
- region A will precede region B in that chain: content will flow into
- region A before it flows into region B.
+ ‘region-order’ of region A is lower than that of region B, then region
+ A will precede region B in that chain: content will flow into region A
+ before it flows into region B.
- <table class=propdef summary="content-order property definition">
+ <table class=propdef summary="region-order property definition">
<tbody>
<tr>
<th>Name:
- <td><dfn id=content-order>content-order</dfn>
+ <td><dfn id=region-order>region-order</dfn>
<tr>
<th>Value:
@@ -1187,9 +1188,9 @@
<ident>)</code>’ value for their ‘<a
href="#content-from"><code class=property>content</code></a>’
property, they are first sorted according to their ‘<a
- href="#content-order"><code class=property>content-order</code></a>’
+ href="#region-order"><code class=property>region-order</code></a>’
value. If multiple regions in have the same ‘<a
- href="#content-order"><code class=property>content-order</code></a>’
+ href="#region-order"><code class=property>region-order</code></a>’
value, they are sorted according to the document order.
<div class="issue stale">
@@ -1200,13 +1201,12 @@
the ‘<code class=css>::grid-cell</code>’ pseudo elements
(e.g., row-major sorting or column major sorting of cells).</div>
- <h3
- id=region-flow-break-properties-break-before-break-after-break-inside><span
- class=secno>3.4. </span>Region flow break properties: ‘<a
- href="#break-before"><code class=property>break-before</code></a>’,
- ‘<a href="#break-after"><code
- class=property>break-after</code></a>’, ‘<a
- href="#break-inside"><code class=property>break-inside</code></a>’</h3>
+ <h3 id=region-flow-break><span class=secno>3.4. </span>Region flow break
+ properties: ‘<a href="#break-before"><code
+ class=property>break-before</code></a>’, ‘<a
+ href="#break-after"><code class=property>break-after</code></a>’,
+ ‘<a href="#break-inside"><code
+ class=property>break-inside</code></a>’</h3>
<p>User agents laying out content in multiple regions, the must determine
where content breaks occur. The problem of breaking content into segments
@@ -1214,8 +1214,8 @@
<p>Each break ends layout in the current region and causes remaining pieces
of content from the named flow to be visually formatted in the following
- region, in the order defined by the ‘<a href="#content-order"><code
- class=property>content-order</code></a>’ computed values. Note that
+ region, in the order defined by the ‘<a href="#region-order"><code
+ class=property>region-order</code></a>’ computed values. Note that
there is no region break in the last region associated with a named flow.
<p>The following extends the ‘<a href="#break-before"><code
@@ -1712,6 +1712,18 @@
<p class=caption>Different values for the region-overflow property</p>
</div>
+ <div class=note>
+ <p>The ‘<a href="#dom-namedflow-overflow"><code
+ class=property>overflow</code></a>’ property is honored on a
+ region: if region content overflows, such as the borders of elements on
+ the last line, the ‘<a href="#dom-namedflow-overflow"><code
+ class=property>overflow</code></a>’ property controls the
+ visibility of the overflowing content. See the ‘<a
+ href="#dom-namedflow-overflow"><code
+ class=property>overflow</code></a>’ property definition (<a
+ href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a>).</p>
+ </div>
+
<h3 id=the-at-region-style-rule><span class=secno>3.6. </span>The @region
rule</h3>
@@ -2044,8 +2056,8 @@
<dd>the region element has no content and is empty. All content from the
<span title=named-flow>named flow</span> was fitted in regions with a
- lower ‘<a href="#content-order"><code
- class=property>content-order</code></a>’ value.
+ lower ‘<a href="#region-order"><code
+ class=property>region-order</code></a>’ value.
<dt>‘<code class=property>undefined</code>’
@@ -2344,9 +2356,9 @@
<ul>
<li>Editorial changes (typos, rephrasings).
- <li>Made ‘<a href="#content-order"><code
- class=property>content-order</code></a>’ a <integer> and not
- a <float> following a working group <a
+ <li>Made ‘<a href="#region-order"><code
+ class=property>region-order</code></a>’ a <integer> and not a
+ <float> following a working group <a
href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html">resolution</a>
<li>Added Alex Mogilevsky as an editor
@@ -2505,6 +2517,18 @@
<li>Removed the section on Integration with other specifications since
specifications that was superfluous especially since there is no specific
integration with multi column, grid or template layout.
+
+ <li>Added a note that regions establish a new block formatting context.
+
+ <li>Renamed content-order to region-order.
+
+ <li>Added a note about overflowing content in regions (e.g., for content
+ with borders).
+
+ <li>Added a note that a region cannot layout content it is part of (to
+ avoid creating a circular dependency) in the flow-from description,
+ specifying that if flow-from references the flow an element is part of,
+ then the element does not format anything visually.
</ul>
<h2 class=no-num id=acknowledgments>Acknowledgments</h2>
@@ -2647,9 +2671,6 @@
<li>content, <a href="#content-from"
title=content><strong>3.2.</strong></a>
- <li>content-order, <a href="#content-order"
- title=content-order><strong>3.3.</strong></a>
-
<li>current-region, <a href="#current-region"
title=current-region><strong>2.3.</strong></a>
@@ -2673,6 +2694,9 @@
<li>region, <a href="#region" title=region>2.1.</a>
+ <li>region-order, <a href="#region-order"
+ title=region-order><strong>3.3.</strong></a>
+
<li><a href="#dom-element-regionoverflow"><code
class=idl>regionOverflow</code></a>, <a
href="#dom-element-regionoverflow"
@@ -2773,13 +2797,13 @@
<td>visual
<tr>
- <th><a class=property href="#content-order">content-order</a>
+ <th><a class=property href="#flow-into">flow-into</a>
- <td><integer>
+ <td><ident> | auto
- <td>0
+ <td>auto
- <td>any block container
+ <td>any element
<td>no
@@ -2788,13 +2812,13 @@
<td>visual
<tr>
- <th><a class=property href="#flow-into">flow-into</a>
+ <th><a class=property href="#region-order">region-order</a>
- <td><ident> | auto
+ <td><integer>
- <td>auto
+ <td>0
- <td>any element
+ <td>any block container
<td>no
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -d -r1.18 -r1.19
--- Overview.src.html 12 Aug 2011 00:13:51 -0000 1.18
+++ Overview.src.html 23 Aug 2011 23:24:30 -0000 1.19
@@ -300,6 +300,8 @@
<h2 id="css-regions-concepts">CSS regions concepts</h2>
+ <p><em>This section is non-normative.</em></p>
+
<h3 id="regions">Regions</h3>
<p class="index" title="region" id="region">A region is an element that
@@ -324,7 +326,7 @@
<p>Elements are placed into a named flow with the 'flow-into' property.
The elements in a named flow are laid out in the chain of regions that
- are associated with this named flow. The 'content-order' property defines how <span title=
+ are associated with this named flow. The 'region-order' property defines how <span title=
"region">regions</span> are organized in to a <span title=
"region-chain">region chain</span>.</p>
@@ -387,7 +389,7 @@
<p><span title=
"region">Regions</span> are organized in to a <span title=
- "region-chain">region chain</span> (see the 'content-order' property).</p>
+ "region-chain">region chain</span> (see the 'region-order' property).</p>
<p>Each region in turn consumes content from its associated <span title=
"named-flow">named flow</span>. The named flow content is
@@ -484,7 +486,7 @@
<p>The main CSS regions module properties are the ‘flow-into’ and 'content'
properties. The ‘flow-into’ property may place an element into a specific named
flow. The ‘content’ property binds a region with a particular named flow. When multiple
- regions are bound to the same flow, the 'content-order' property determines
+ regions are bound to the same flow, the 'region-order' property determines
the order in which content flows into the sequence of regions. This
sequences of regions is called a <dfn>region chain</dfn>.</p>
@@ -767,18 +769,19 @@
<dd>If the element is not a <a href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container box</a>, the value evaluates to 'normal'. <br />
Otherwise, the element becomes a <span>region</span> and is ordered in a
<span>region chain</span> according to its document order and
- 'content-order' property. The content from the flow with the <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
- name will be <a href="#region-flow-break-properties-break-before-break-after-break-inside">broken into segments</a> and visually formatted in the
+ 'region-order' property. The content from the flow with the <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
+ name will be <a href="#region-flow-break">broken into segments</a> and visually formatted in the
<a href="http://www.w3.org/TR/CSS21/visuren.html#principal-box">principal boxes</a> of the regions in the region chain. If there is no flow with name
- <ident>, then the element does not format any content visually.
- <br />
+ <ident>, then the element does not format any content visually. <br/>Likewise, if
+ the element is part of the flow with name <ident>, then
+ the element does not format any content visually.
+ <br />
This might be expanded in future versions of the specification
to allow other types of containers to receive flow content.
</dd>
</dl>
- <p>When the 'content' property is set to 'none', 'from-flow', <string>, <uri>,
- <counter>, 'attr(<identifier>)', open-quote, close-quote, no-open-quote or no-close-quote, the document children of the element are not visually formatted unless they are directed to a named flow
+ <p>When the 'content' property is set to a value other than 'normal', the element's document children are not visually formatted unless they are directed to a named flow
referenced by one or more regions.</p>
<div class="note">
@@ -874,6 +877,8 @@
<p><span title="region">Regions</span> create a new stacking context.</p>
+ <p><span title="region">Regions</span> establish a new <a href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block formatting Context</a>.</p>
+
<div class="note">
<p><em>This note is informative.</em></p>
<p>With regions, an element may be split across multiple regions and these
@@ -924,19 +929,19 @@
</pre>
</div>
- <h3 id="the-content-order-property">The 'content-order' property</h3>
+ <h3 id="the-region-order-property">The 'region-order' property</h3>
<p>Defines the ordering of the chain of regions into which content flows.
If region A and region B are in the same chain of regions and the
- ‘content-order’ of region A is lower than that of region B, then region A
+ ‘region-order’ of region A is lower than that of region B, then region A
will precede region B in that chain: content will flow into region A before
it flows into region B.</p>
- <table class="propdef" summary="content-order property definition">
+ <table class="propdef" summary="region-order property definition">
<tr>
<th>Name:</th>
- <td><dfn id="content-order">content-order</dfn></td>
+ <td><dfn id="region-order">region-order</dfn></td>
</tr>
<tr>
@@ -992,7 +997,7 @@
<p>If two or more regions with the same 'flow-from( <ident>)' value
for their 'content' property, they are first sorted according to their
- 'content-order' value. If multiple regions in have the same 'content-order'
+ 'region-order' value. If multiple regions in have the same 'region-order'
value, they are sorted according to the document order.</p>
<div class="issue stale">
@@ -1006,7 +1011,7 @@
</div>
<h3 id=
- "region-flow-break-properties-break-before-break-after-break-inside">Region
+ "region-flow-break">Region
flow break properties: 'break-before', 'break-after', 'break-inside'</h3>
<p>User agents laying out content in multiple regions, the must
@@ -1016,7 +1021,7 @@
<p>Each break ends layout in the current region and causes remaining pieces
of content from the named flow to be visually formatted in the following
- region, in the order defined by the 'content-order' computed values. Note
+ region, in the order defined by the 'region-order' computed values. Note
that there is no region break in the last region associated with a named
flow.</p>
@@ -1536,6 +1541,14 @@
<p class="caption">Different values for the region-overflow
property</p>
</div>
+
+ <div class="note">
+ <p>The 'overflow' property is honored on a region: if region content overflows,
+ such as the borders of elements on the
+ last line, the 'overflow' property controls the visibility of the overflowing
+ content. See the 'overflow' property definition
+ ([[CSS21]]).</p>
+ </div>
<h3 id="the-at-region-style-rule">The @region rule</h3>
@@ -1835,7 +1848,7 @@
<dd>the region element has no content and is empty. All content from
the <span title="named-flow">named flow</span> was fitted in regions
- with a lower 'content-order' value.</dd>
+ with a lower 'region-order' value.</dd>
<dt>'undefined'</dt>
<dd>The element is not a <span>region</span>.</dd>
@@ -2094,7 +2107,7 @@
<ul>
<li>Editorial changes (typos, rephrasings).</li>
- <li>Made 'content-order' a <integer> and not a <float> following a working group
+ <li>Made 'region-order' a <integer> and not a <float> following a working group
<a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0329.html">resolution</a></li>
<li>Added Alex Mogilevsky as an editor</li>
<li>Flow names became <indent> instead of <string> following a working group
@@ -2170,6 +2183,13 @@
<li>Removed the section on Integration with other specifications since specifications that
was superfluous especially since there is no specific integration with multi column,
grid or template layout.</li>
+ <li>Added a note that regions establish a new block formatting context.</li>
+ <li>Renamed content-order to region-order.</li>
+ <li>Added a note about overflowing content in regions (e.g., for content with borders).</li>
+ <li>Added a note that a region cannot layout content it is part of (to avoid creating a
+ circular dependency) in the flow-from description, specifying that if flow-from
+ references the flow an element is part of, then the element does not format
+ anything visually.</li>
</ul>
<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
Received on Tuesday, 23 August 2011 23:24:35 UTC