- From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 30 Sep 2011 22:31:29 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv29256
Modified Files:
Overview.html Overview.src.html
Log Message:
Included editorial review comments from Alan Stearns
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -d -r1.20 -r1.21
--- Overview.html 30 Sep 2011 20:20:30 -0000 1.20
+++ Overview.html 30 Sep 2011 22:31:27 -0000 1.21
@@ -138,68 +138,68 @@
<li><a href="#regions-flow-breaking-rules"><span class=secno>2.3.
</span>Regions flow breaking rules</a>
-
- <li><a href="#relation-to-document-events"><span class=secno>2.4.
- </span>Relation to document events</a>
</ul>
- <li><a href="#properties-and-rules"><span class=secno>3. </span>Properties
+ <li><a href="#relation-to-document-events"><span class=secno>3.
+ </span>Relation to document events</a>
+
+ <li><a href="#properties-and-rules"><span class=secno>4. </span>Properties
and rules</a>
<ul class=toc>
- <li><a href="#the-flow-into-property"><span class=secno>3.1. </span>The
+ <li><a href="#the-flow-into-property"><span class=secno>4.1. </span>The
‘<code class=property>flow-into</code>’ property</a>
- <li><a href="#the-flow-from-property"><span class=secno>3.2. </span>The
+ <li><a href="#the-flow-from-property"><span class=secno>4.2. </span>The
‘<code class=property>flow-from</code>’ property</a>
<ul class=toc>
- <li><a href="#auto-width-on-regions"><span class=secno>3.2.1.
+ <li><a href="#auto-width-on-regions"><span class=secno>4.2.1.
</span>Auto width on regions</a>
- <li><a href="#auto-height-on-regions"><span class=secno>3.2.2.
+ <li><a href="#auto-height-on-regions"><span class=secno>4.2.2.
</span>Auto height on regions</a>
</ul>
- <li><a href="#region-flow-break"><span class=secno>3.3. </span>Region
+ <li><a href="#region-flow-break"><span class=secno>4.3. </span>Region
flow break properties: ‘<code
class=property>break-before</code>’, ‘<code
class=property>break-after</code>’, ‘<code
class=property>break-inside</code>’</a>
- <li><a href="#the-region-overflow-property"><span class=secno>3.4.
+ <li><a href="#the-region-overflow-property"><span class=secno>4.4.
</span>The region-overflow property</a>
- <li><a href="#the-at-region-style-rule"><span class=secno>3.5.
+ <li><a href="#the-at-region-style-rule"><span class=secno>4.5.
</span>The @region rule</a>
</ul>
- <li><a href="#pseudo_elements"><span class=secno>4.
+ <li><a href="#pseudo_elements"><span class=secno>5.
</span>Pseudo-elements</a>
<ul class=toc>
- <li><a href="#processing-model"><span class=secno>4.1. </span>Processing
+ <li><a href="#processing-model"><span class=secno>5.1. </span>Processing
model</a>
</ul>
- <li><a href="#cssom_view_and_css_regions"><span class=secno>5.
+ <li><a href="#cssom_view_and_css_regions"><span class=secno>6.
</span>CSSOM view and CSS regions</a>
<ul class=toc>
- <li><a href="#the-namedflow-interface"><span class=secno>5.1. </span>The
+ <li><a href="#the-namedflow-interface"><span class=secno>6.1. </span>The
NamedFlow interface</a>
- <li><a href="#extension-to-the-element-interface"><span class=secno>5.2.
+ <li><a href="#extension-to-the-element-interface"><span class=secno>6.2.
</span>Extension to the Element interface</a>
- <li><a href="#region-flow-layout-events"><span class=secno>5.3.
+ <li><a href="#region-flow-layout-events"><span class=secno>6.3.
</span>Region flow layout events</a>
</ul>
- <li><a href="#relation-to-other-specifications"><span class=secno>6.
+ <li><a href="#relation-to-other-specifications"><span class=secno>7.
</span>Relation to other specifications</a>
- <li><a href="#conformance"><span class=secno>7. </span>Conformance</a>
+ <li><a href="#conformance"><span class=secno>8. </span>Conformance</a>
- <li><a href="#changes"><span class=secno>8. </span>Changes</a>
+ <li><a href="#changes"><span class=secno>9. </span>Changes</a>
<ul class=toc>
- <li><a href="#changes_from_June_09_2011"><span class=secno>8.1.
+ <li><a href="#changes_from_June_09_2011"><span class=secno>9.1.
</span>Changes from June 09<sup>th</sup> 2011 version</a>
</ul>
@@ -409,9 +409,6 @@
‘<a href="#flow-from"><code
class=property>flow-from</code></a>’ property).
- <p>A <span title=region>region</span>‘<code class=css>s intrinsic
- width is zero.</code>
-
<div class="issue moved">
<p>See <a
href="http://wiki.csswg.org/spec/css3-regions#issue-2-auto-sizing-of-regions"></a></p>
@@ -427,7 +424,8 @@
elements associated with a flow with a given identifier. Elements in a
named flow are ordered according to the document order.
- <p>Elements are placed into a named flow with the ’flow-into'
+ <p>Elements are placed into a named flow with the ‘<a
+ href="#flow-into"><code class=property>flow-into</code></a>’
property. The elements in a named flow are laid out in the chain of
regions that are associated with this named flow. <span
title=region>Regions</span> are organized in to a <span
@@ -455,15 +453,17 @@
in the <dfn id=current-region title=current-region>current region</dfn>
until a natural or forced region break occurs, at which point the <a
href="#current-region" title=current-region>current region</a> becomes the
- next one in the <span title=region-chain>region chain</span>. If there is
- no more <span>region</span> in the region chain and there is still content
- in the flow, the positioning of the remaining content is controlled by the
- ‘<a href="#region-overflow"><code
+ next one in the <span title=region-chain>region chain</span>. If there are
+ no more <span>region</span>s in the region chain and there is still
+ content in the flow, the positioning of the remaining content is
+ controlled by the ‘<a href="#region-overflow"><code
class=property>region-overflow</code></a>’ property on the last
<span>region</span> in the chain.
- <h3 id=relation-to-document-events><span class=secno>2.4. </span>Relation
- to document events</h3>
+ <h2 id=relation-to-document-events><span class=secno>3. </span>Relation to
+ document events</h2>
+
+ <p><em>This section is normative.</em>
<p>The CSS regions module does not alter the normal processing of events in
the document tree. In particular, if an event occurs on an element that is
@@ -471,10 +471,12 @@
href="http://www.w3.org/TR/DOM-Level-3-Events/#dom-event-architecture">event's
bubble and capture phases</a> happen following the document tree order.
- <h2 id=properties-and-rules><span class=secno>3. </span>Properties and
+ <h2 id=properties-and-rules><span class=secno>4. </span>Properties and
rules</h2>
- <h3 id=the-flow-into-property><span class=secno>3.1. </span>The ‘<a
+ <p><em>This section is normative.</em>
+
+ <h3 id=the-flow-into-property><span class=secno>4.1. </span>The ‘<a
href="#flow-into"><code class=property>flow-into</code></a>’
property</h3>
@@ -639,7 +641,7 @@
class=css>::after</code> is undefined. This may change depending on
implementation feedback.
- <h3 id=the-flow-from-property><span class=secno>3.2. </span>The ‘<a
+ <h3 id=the-flow-from-property><span class=secno>4.2. </span>The ‘<a
href="#flow-from"><code class=property>flow-from</code></a>’
property</h3>
@@ -866,14 +868,14 @@
</pre>
</div>
- <h4 id=auto-width-on-regions><span class=secno>3.2.1. </span>Auto width on
+ <h4 id=auto-width-on-regions><span class=secno>4.2.1. </span>Auto width on
regions</h4>
<p>If a region's ‘<code class=property>width</code>’ property
is computed to ‘<code class=property>auto</code>’, its
resolved width is ‘<code class=css>0</code>’.
- <h4 id=auto-height-on-regions><span class=secno>3.2.2. </span>Auto height
+ <h4 id=auto-height-on-regions><span class=secno>4.2.2. </span>Auto height
on regions</h4>
<p>If a region's ‘<code class=property>height</code>’ property
@@ -884,13 +886,13 @@
href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a>) where:
<ul>
- <li>Children, in the context of CSS regions, means the reminder of the
+ <li>Children, in the context of CSS regions, means the remainder of the
regions's associated flow.
<li>Last line box means the last line box in the region's associated flow.
</ul>
- <h3 id=region-flow-break><span class=secno>3.3. </span>Region flow break
+ <h3 id=region-flow-break><span class=secno>4.3. </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>’,
@@ -1115,7 +1117,7 @@
class=property>overflow</code></a>’ property specified on the region
element should be used to determine how to render the overflow.
- <h3 id=the-region-overflow-property><span class=secno>3.4. </span>The
+ <h3 id=the-region-overflow-property><span class=secno>4.4. </span>The
region-overflow property</h3>
<table class=propdef summary="break-after property definition">
@@ -1264,7 +1266,7 @@
href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a>).</p>
</div>
- <h3 id=the-at-region-style-rule><span class=secno>3.5. </span>The @region
+ <h3 id=the-at-region-style-rule><span class=secno>4.5. </span>The @region
rule</h3>
<div class=issue-marker><a
@@ -1481,7 +1483,9 @@
order</a> as defined in <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>.
- <h2 id="pseudo_elements"><span class=secno>4. </span>Pseudo-elements</h2>
+ <h2 id="pseudo_elements"><span class=secno>5. </span>Pseudo-elements</h2>
+
+ <p><em>This section is normative.</em>
<p>It can be useful to visually mark the content to highlight that a
content thread is flowing from region to region. For example, a marker
@@ -1495,7 +1499,7 @@
rel=biblioentry>[SELECT]<!--{{!SELECT}}--></a>) let content authors mark
the beginning and end of a region with such markers.
- <h3 id=processing-model><span class=secno>4.1. </span>Processing model</h3>
+ <h3 id=processing-model><span class=secno>5.1. </span>Processing model</h3>
<p>The ‘<code class=css>::before</code>’ content is laid out in
the region prior to any other content coming from the flow. Note that it
@@ -1522,9 +1526,11 @@
and can accommodate for the ‘<code class=css>::after</code>’
box.
- <h2 id="cssom_view_and_css_regions"><span class=secno>5. </span>CSSOM view
+ <h2 id="cssom_view_and_css_regions"><span class=secno>6. </span>CSSOM view
and CSS regions</h2>
+ <p><em>This section is normative.</em>
+
<p>Since content may flow into multiple regions, authors need a way to
determine if there are enough regions to flow all the content from a named
flow. This is especially important considering that the size of regions
@@ -1545,7 +1551,7 @@
regions it is part of.</p>
</div>
- <h3 id=the-namedflow-interface><span class=secno>5.1. </span>The NamedFlow
+ <h3 id=the-namedflow-interface><span class=secno>6.1. </span>The NamedFlow
interface</h3>
<p>The <code class=idl>getFlowByName<a
@@ -1578,7 +1584,7 @@
interface, authors can easily check if all content has been fitted into
existing regions. If it has, the overflow property would be false.
- <h3 id=extension-to-the-element-interface><span class=secno>5.2.
+ <h3 id=extension-to-the-element-interface><span class=secno>6.2.
</span>Extension to the Element interface</h3>
<p>When an region is an actual <a
@@ -1671,7 +1677,7 @@
class=property>multi-view</code>’ context as suggested by Alex.</p>
</div>
- <h3 id=region-flow-layout-events><span class=secno>5.3. </span>Region flow
+ <h3 id=region-flow-layout-events><span class=secno>6.3. </span>Region flow
layout events</h3>
<p>Region <a
@@ -1731,7 +1737,7 @@
</ul>
</table>
- <h2 id=relation-to-other-specifications><span class=secno>6.
+ <h2 id=relation-to-other-specifications><span class=secno>7.
</span>Relation to other specifications</h2>
<p>This specification is related to other specifications as described in
@@ -1753,11 +1759,11 @@
flowing in separate regions.
</ol>
- <h2 id=conformance><span class=secno>7. </span>Conformance</h2>
+ <h2 id=conformance><span class=secno>8. </span>Conformance</h2>
- <h2 id=changes><span class=secno>8. </span>Changes</h2>
+ <h2 id=changes><span class=secno>9. </span>Changes</h2>
- <h3 id="changes_from_June_09_2011"><span class=secno>8.1. </span>Changes
+ <h3 id="changes_from_June_09_2011"><span class=secno>9.1. </span>Changes
from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20110609/">June
09<sup>th</sup> 2011</a> version</h3>
@@ -1770,7 +1776,7 @@
<li>Added Alex Mogilevsky as an editor
- <li>Flow names became <indent> instead of <string> following a
+ <li>Flow names became <ident> instead of <string> following a
working group <a
href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a>
@@ -2091,45 +2097,45 @@
<ul class=indexlist>
<li>break-after, <a href="#break-after"
- title=break-after><strong>3.3.</strong></a>
+ title=break-after><strong>4.3.</strong></a>
<li>break-before, <a href="#break-before"
- title=break-before><strong>3.3.</strong></a>
+ title=break-before><strong>4.3.</strong></a>
<li>break-inside, <a href="#break-inside"
- title=break-inside><strong>3.3.</strong></a>
+ title=break-inside><strong>4.3.</strong></a>
<li>current-region, <a href="#current-region"
title=current-region><strong>2.3.</strong></a>
<li>flow-from, <a href="#flow-from"
- title=flow-from><strong>3.2.</strong></a>
+ title=flow-from><strong>4.2.</strong></a>
<li>flow-into, <a href="#flow-into"
- title=flow-into><strong>3.1.</strong></a>
+ title=flow-into><strong>4.1.</strong></a>
<li>getRegionFlowRanges, <a href="#dom-element-getregionflowranges"
- title=getRegionFlowRanges><strong>5.2.</strong></a>
+ title=getRegionFlowRanges><strong>6.2.</strong></a>
<li><a href="#dom-namedflow"><code class=idl>NamedFlow</code></a>, <a
- href="#dom-namedflow" title=NamedFlow><strong>5.1.</strong></a>
+ href="#dom-namedflow" title=NamedFlow><strong>6.1.</strong></a>
<li><a href="#dom-namedflow-overflow"><code class=idl>overflow</code></a>,
<a href="#dom-namedflow-overflow"
- title=overflow><strong>5.1.</strong></a>
+ title=overflow><strong>6.1.</strong></a>
<li>region, <a href="#region" title=region>2.1.</a>
<li><a href="#dom-element-regionoverflow"><code
class=idl>regionOverflow</code></a>, <a
href="#dom-element-regionoverflow"
- title=regionOverflow><strong>5.2.</strong></a>
+ title=regionOverflow><strong>6.2.</strong></a>
<li>region-overflow, <a href="#region-overflow"
- title=region-overflow><strong>3.4.</strong></a>
+ title=region-overflow><strong>4.4.</strong></a>
<li>specified flow, <a href="#specified-flow" title="specified
- flow"><strong>3.1.</strong></a>
+ flow"><strong>4.1.</strong></a>
</ul>
<!--end-index-->
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -d -r1.22 -r1.23
--- Overview.src.html 30 Sep 2011 20:20:30 -0000 1.22
+++ Overview.src.html 30 Sep 2011 22:31:27 -0000 1.23
@@ -268,8 +268,6 @@
"http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block container
box</a> and has an associated <em>named flow</em> (see the 'flow-from'
property).</p>
-
- <p>A <span title="region">region</span>'s intrinsic width is zero.</p>
<div class="issue moved">
<p>See <a href="http://wiki.csswg.org/spec/css3-regions#issue-2-auto-sizing-of-regions"></a></p>.
@@ -310,15 +308,17 @@
positioned in the <dfn title="current-region">current region</dfn> until a
natural or forced region break occurs, at which point the <span title=
"current-region">current region</span> becomes the next one in the
- <span title="region-chain">region chain</span>. If there is no more
- <span>region</span> in the region chain and there is still content in the
+ <span title="region-chain">region chain</span>. If there are no more
+ <span>region</span>s in the region chain and there is still content in the
flow, the positioning of the remaining content is controlled by the
'region-overflow' property on the last <span>region</span> in the
chain.</p>
- <h3 id="relation-to-document-events">Relation to document events</h3>
+ <h2 id="relation-to-document-events">Relation to document events</h2>
+ <p><em>This section is normative.</em></p>
+
<p>The CSS regions module does not alter the normal processing of
events in the document tree. In particular, if an event occurs on an
element that is part of a named flow, the <a href=
@@ -327,6 +327,8 @@
<h2 id="properties-and-rules">Properties and rules</h2>
+ <p><em>This section is normative.</em></p>
+
<h3 id="the-flow-into-property">The 'flow-into' property</h3>
<p>The ‘flow-into’ property can place an element into a named flow. Elements that
@@ -695,7 +697,7 @@
described in the <a href="http://www.w3.org/TR/CSS2/visudet.html#Computing_heights_and_margins">Computing heights and margins</a> section of the CSS 2.1 specification (see [[CSS21]]) where:</p>
<ul>
- <li>Children, in the context of CSS regions, means the reminder of the regions's associated flow.</li>
+ <li>Children, in the context of CSS regions, means the remainder of the regions's associated flow.</li>
<li>Last line box means the last line box in the region's associated flow.</li>
</ul>
@@ -1257,6 +1259,8 @@
order</a> as defined in [[!CSS21]].</p>
<h2 id="pseudo_elements">Pseudo-elements</h2>
+
+ <p><em>This section is normative.</em></p>
<p>It can be useful to visually mark the content to highlight
that a content thread is flowing from region to region. For example, a marker such
@@ -1286,6 +1290,8 @@
<h2 id="cssom_view_and_css_regions">CSSOM view and CSS regions</h2>
+ <p><em>This section is normative.</em></p>
+
<p>Since content may flow into multiple regions, authors need a way to
determine if there are enough regions to flow all the content from a named
flow. This is especially important considering that the size of regions may
@@ -1487,7 +1493,7 @@
<li>Made 'content-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
+ <li>Flow names became <ident> instead of <string> following a working group
<a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">resolution</a></li>
<li>Removed issue about possibly altering the DOM Events model for region events following
a working group
Received on Friday, 30 September 2011 22:31:36 UTC