- From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 24 Jan 2012 19:52:48 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv8896
Modified Files:
Overview.html Overview.src.html
Log Message:
Editorial changes, as per Fantasai's comments at http://lists.w3.org/Archives/Public/www-style/2011Dec/0472.html
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -d -r1.37 -r1.38
--- Overview.html 24 Jan 2012 03:15:29 -0000 1.37
+++ Overview.html 24 Jan 2012 19:52:46 -0000 1.38
@@ -610,10 +610,10 @@
<dt><a
href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>
- <dd>The element is placed into the flow with the name ‘<code
- class=css><ident></code>’. The element is said to have a <dfn
- id=specified-flow>specified flow</dfn>. The values ‘<code
- class=property>none</code>’, ‘<code
+ <dd>The element is taken out of its parent's flow and placed into the flow
+ with the name ‘<code class=css><ident></code>’. The
+ element is said to have a <dfn id=specified-flow>specified flow</dfn>.
+ The values ‘<code class=property>none</code>’, ‘<code
class=property>inherit</code>’, ‘<code
class=property>default</code>’, ‘<code
class=property>auto</code>’ and ‘<code
@@ -812,9 +812,6 @@
href="http://www.w3.org/TR/CSS2/visuren.html#block-formatting">block
formatting Context</a>.
- <p>If the ‘<code class=property>content</code>’ property is
- defined on a region, it has no effect on the region's visual formatting.
-
<div class=note><span class=note-prefix>Note </span>
<p>With regions, an element may be split across multiple regions and these
regions may overlap (for example if they are absolutely positioned). So
@@ -1787,6 +1784,10 @@
<li>Removed "This section is informative" paragraphs since in CSS
specifications notes are always informative.
+
+ <li>Reworded the text about flow-into: <ident> and removed obsolete
+ text about the interaction with the ‘<code
+ class=property>content</code>’ property.
</ul>
<h3 id="changes_from_June_09_2011"><span class=secno>10.2. </span>Changes
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- Overview.src.html 24 Jan 2012 03:15:30 -0000 1.42
+++ Overview.src.html 24 Jan 2012 19:52:46 -0000 1.43
@@ -456,7 +456,8 @@
<dt><a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a></dt>
- <dd>The element is placed into the flow with the name '<ident>'. The
+ <dd>The element is taken out of its parent's flow and placed into the
+ flow with the name '<ident>'. The
element is said to have a <dfn id="specified-flow">specified
flow</dfn>. The values 'none', 'inherit', 'default', 'auto' and 'initial' are invalid flow
names.</dd>
@@ -620,9 +621,6 @@
<p><span title="region">Regions</span> create a new <a href="http://www.w3.org/TR/CSS2/visuren.html#z-index">stacking context</a>. <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>
- <p>If the 'content' property is defined on a region, it has no effect on the region's
- visual formatting.</p>
-
<div class="note"><span class="note-prefix">Note </span>
<p>With regions, an element may be split across multiple regions and these
regions may overlap (for example if they are absolutely positioned).
@@ -1474,6 +1472,8 @@
<li>Removed "This section is normative" paragraphs since in CSS specifications, sections are normative unless
otherwise specified.</li>
<li>Removed "This section is informative" paragraphs since in CSS specifications notes are always informative.</li>
+ <li>Reworded the text about flow-into: <ident> and removed obsolete text about the interaction with the
+ 'content' property.</li>
</ul>
Received on Tuesday, 24 January 2012 19:52:50 UTC