- From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 12 Aug 2011 00:10:23 +0000
- To: public-css-commits@w3.org
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv2311
Modified Files:
Overview.html Overview.src.html alternate-spec-style.css
Log Message:
Completed full review. Commented out preferred/allowed/best breaks. Commented out integration with other specs. section
Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -d -r1.14 -r1.15
--- Overview.html 10 Aug 2011 00:22:34 -0000 1.14
+++ Overview.html 12 Aug 2011 00:10:21 -0000 1.15
@@ -6,7 +6,7 @@
http-equiv=X-UA-Compatible>
<meta content="text/html; charset=utf-8" http-equiv=Content-Type>
- <title>CSS Regions Module</title>
+ <title>CSS regions Module</title>
<link href="http://dev.w3.org/csswg/default.css" rel=stylesheet
type="text/css">
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel=Stylesheet
@@ -23,15 +23,15 @@
<p><a href="http://www.w3.org/"><img alt=W3C height=48
src="http://www.w3.org/Icons/w3c_home" width=72></a> <!--end-logo--></p>
[...1283 lines suppressed...]
title="flow-from(<ident>)"><strong>3.2.</strong></a>
@@ -2737,9 +2664,6 @@
<li>region, <a href="#region" title=region>2.1.</a>
- <li>region chain, <a href="#region-chain" title="region
- chain"><strong>3.</strong></a>
-
<li><a href="#dom-element-regionoverflow"><code
class=idl>regionOverflow</code></a>, <a
href="#dom-element-regionoverflow"
@@ -2857,7 +2781,7 @@
<tr>
<th><a class=property href="#flow-into">flow-into</a>
- <td><ident>
+ <td><ident> | auto
<td>auto
Index: alternate-spec-style.css
===================================================================
RCS file: /sources/public/csswg/css3-regions/alternate-spec-style.css,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -d -r1.4 -r1.5
--- alternate-spec-style.css 1 Jul 2011 22:59:44 -0000 1.4
+++ alternate-spec-style.css 12 Aug 2011 00:10:21 -0000 1.5
@@ -58,8 +58,10 @@
div.note {
margin-top: 1em;
padding: 0.5em;
+ border: 1px solid #ECF4F8;
border-left: 5px solid #1C75BC;
padding-left: 1em;
+ padding-bottom: 1em;
position: relative;
background: #F3FAFF;
}
@@ -151,4 +153,8 @@
.event-desc th {
text-align: left;
padding: 0.5ex;
+}
+
+.resolved, .moved, .stale {
+ display: none;
}
\ No newline at end of file
Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- Overview.src.html 10 Aug 2011 00:22:34 -0000 1.16
+++ Overview.src.html 12 Aug 2011 00:10:21 -0000 1.17
@@ -6,7 +6,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
- <title>CSS Regions Module</title>
+ <title>CSS regions Module</title>
<link href="http://dev.w3.org/csswg/default.css" rel="stylesheet" type=
"text/css">
<link href="http://www.w3.org/StyleSheets/TR/W3C-ED.css" rel="Stylesheet"
@@ -27,7 +27,7 @@
<p><a href="http://www.w3.org/"><img alt="W3C" height="48" src=
"http://www.w3.org/Icons/w3c_home" width="72"></a> <!--end-logo--></p>
- <h1 id="css-regions-module">CSS Regions Module</h1>
+ <h1 id="css-regions-module">CSS regions Module</h1>
<h2 class="no-num no-toc" id="longstatus-date">Editor's Draft
[DATE]</h2>
@@ -91,11 +91,11 @@
<h2 class="no-num no-toc" id="abstract">Abstract</h2>
- <strong>EDITS IN PROGRESS: NOT READY FOR REVIEW</strong>
+ <strong>CHANGES IN PROGRESS, NOT READY FOR REVIEW</strong>
- <p>The CSS Regions module allows content to flow across multiple areas
+ <p>The CSS regions module allows content to flow across multiple areas
called regions. The regions do not necessarily follow the document order.
- The CSS Regions module provides an advanced content flow mechanism, which
+ The CSS regions module provides an advanced content flow mechanism, which
can be combined with positioning schemes as defined by other CSS modules
such as the Multi-Column Module [[CSS3COL]] or the Grid Layout Module
[[CSS3-GRID-LAYOUT]] to position the regions where content flows.</p>
@@ -134,11 +134,11 @@
<p>Capturing the complex layouts of a typical magazine, newspaper, or
textbook requires capabilities beyond those available in existing CSS
- modules. This is the purpose of the CSS Regions module.</p>
+ modules. This is the purpose of the CSS regions module.</p>
<p> </p>
- <p>The CSS Regions module can be seen as an extension of the concept of
+ <p>The CSS regions module can be seen as an extension of the concept of
multi-column elements. With CSS Multi-column layout [[CSS3COL]], columns
share the same dimensions and define column boxes organized in rows.
Content flows from one column to the next.</p>
@@ -177,13 +177,13 @@
1, 2, 3 and 4.</p>
<pre>
<div <em>id="article"</em>>
-<h1>Introduction</h1>
- <p>This is an example ...</p>
+ <h1>Introduction</h1>
+ <p>This is an example ...</p>
-<h1>More Details</h1>
- <p>This illustrates ...</p>
- <p>Then, the example ...</p>
- <p>Finally, this ...</p>
+ <h1>More Details</h1>
+ <p>This illustrates ...</p>
+ <p>Then, the example ...</p>
+ <p>Finally, this ...</p>
</div>
</pre>
@@ -200,15 +200,12 @@
<p class="caption">Sample rendering for desired layout</p>
</div>
- <p>Since the CSS Regions module is independent of the layout of regions and
+ <p>Since the CSS regions module is independent of the layout of regions and
the mechanism used to create them, the following assumes there is a CSS
selector for the regions and, for the purpose of the example, the selectors
for regions 1, 2, 3 and 4 show as ''<region1_sel>'',
''<region2_sel>'', ''<region3_sel>'' and
- ''<region4_sel>'' respectively. Such a selector could be an id
- selector (e.g., ''#region_1'') or a grid cell selector (e.g.,
- ''#myGrid::grid-cell([cell-name])'') if using the CSS Grid Layout module,
- for example.</p>
+ ''<region4_sel>'' respectively.</p>
<div class="example">
<pre>
@@ -225,11 +222,11 @@
</style>
</pre>
</div>
-
- <p>The above stylesheet directs the ''#article'' element to a named flow
- called 'article_flow' by setting the 'flow-into' property. Then, content is
- "poured" from that named flow into the desired regions by setting the
- regions' 'content' property to ''flow-from(article_flow)''.</p>
+
+ <p>The 'article_flow' value on the 'flow-into' property directs the ''#article''
+ element to the 'article_flow' named flow. Setting the regions' content property
+ to 'flow-from(article_flow)' associates these regions with the named flow: the flow is
+ ''poured'' into the desired regions.</p>
<h3 id="region-styling">Regions styling</h3>
@@ -264,7 +261,7 @@
/*
* Additional styling to apply to content when it falls into
- * region_1
+ * region1
*/
<strong>@region <region1_sel> {</strong>
#article::region-lines {
@@ -313,9 +310,10 @@
<p>A <span title="region">region</span>'s intrinsic width is zero.</p>
- <div class="issue">
- There was a recent discussion on intrinsic sizing of regions which
- <a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0629.html">has not been resolved</a>.
+ <div class="issue moved">
+ <p>See <a href="http://wiki.csswg.org/spec/css3-regions#issue-2-auto-sizing-of-regions"></a></p>.
+ <p>There was a recent discussion on intrinsic sizing of regions which
+ <a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0629.html">has not been resolved</a></p>.
</div>
<h3 id="named-flow">Named flow</h3>
@@ -357,7 +355,7 @@
<p> </p>
- <p>The CSS Regions module generalizes the concept of flow by adding the
+ <p>The CSS regions module generalizes the concept of flow by adding the
concept of a <em>named flow</em>. This module lets authors explicitly place
elements into a <em>named flow</em>.</p>
@@ -382,16 +380,14 @@
<h3 id="regions-flow-breaking-rules">Regions flow breaking rules</h3>
<p>Breaking a named flow across multiple regions is similar to breaking a
- document's content across multiple pages. One difference is that
+ document's content across multiple pages (see [[CSS3PAGE]]) or a multi-column element's content
+ across column boxes (see [[CSS3COL]]). One difference is that
page boxes are generated based on the available content whereas regions are
a predefined set of recipient boxes for the named flow content.</p>
- <h4 id="breaking-a-named-flow-and-determining-the-current-flow-region">
- Breaking a named flow and determining the current flow region</h4>
-
- <p>The 'content-order' property defines how <span title=
- "region">regions</span> are organized in to a <span title=
- "region-chain">region chain</span>.</p>
+ <p><span title=
+ "region">Regions</span> are organized in to a <span title=
+ "region-chain">region chain</span> (see the 'content-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
@@ -474,9 +470,7 @@
-->
<h3 id="relation-to-document-events">Relation to document events</h3>
- <p><em>This section is non-normative.</em></p>
-
- <p>The CSS Region module does not alter in any way the normal processing of
+ <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=
"http://www.w3.org/TR/DOM-Level-3-Events/#dom-event-architecture">event's
@@ -484,27 +478,26 @@
<h2 id="properties-and-rules">Properties and rules</h2>
- <p>The main CSS Regions module properties are the ‘flow’ and 'content'
- properties. The ‘flow’ property places an element into a specific named
- flow or lets the <a href="auto-flows">automatic flow assignment</a> take
- place. The ‘content’ property binds a region with a flow. When multiple
+<!-- Commented out following section because it was redundant with the introduction -->
+
+<!--
+ <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
the order in which content flows into the sequence of regions. This
sequences of regions is called a <dfn>region chain</dfn>.</p>
- <p> </p>
-
- <p>The way in which the content is broken into segments that fit in a
- region can be controlled by the “break” properties. Finally, styling that
- is unique to the region can be specified by ‘region-style’ rules.</p>
+ <p>The “break-*” properties control how content is broken into segments which are
+ then fitted in regions.</p>
+
+ <p>Styling that is unique to the region can be specified by ‘@region’ rules.</p>
+-->
<h3 id="the-flow-into-property">The 'flow-into' property</h3>
- <p>The ‘flow’ property places an element into a named flow or automatically
- places it in the appropriate flow (see the <a href=
- "#formatting-model-considerations">Visual Formatting Model and Flows</a>
- section). Elements that belong to the same flow are laid out in the regions
- associated with that flow.</p>
+ <p>The ‘flow-into’ property can place an element into a named flow. Elements that
+ belong to the same flow are laid out in the regions associated with that flow.</p>
<table class="propdef" summary="flow property definition">
<tr>
@@ -516,7 +509,7 @@
<tr>
<th>Value:</th>
- <td><ident></td>
+ <td><ident> | auto</td>
</tr>
<tr>
@@ -559,15 +552,13 @@
<dl>
<dt>auto</dt>
- <dd>The element is automatically moved to the appropriate flow
- according to the <a href="#formatting_model_considerations">Visual
- Formatting Model and Flows</a> definitions.</dd>
+ <dd>The element is not moved to a named flow and normal CSS processing takes place.</dd>
<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 (appended) to the flow with that name. The
+ <dd>The element is 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' and 'initial' and invalid flow
+ flow</dfn>. The values 'none', 'inherit', 'default' and 'initial' are invalid flow
names.</dd>
</dl>
@@ -580,76 +571,25 @@
specified flow.</p>
<p>If an element has a the same specified flow value as one of its
- ancestors, it is moved out of its parent's normal flow and becomes a
- sibling of it's ancestor for the purpose of layout in the regions taking
- content from this flow.</p>
+ ancestors, it becomes a
+ sibling of it's ancestor for the purpose of layout in the regions laying out content
+ content from that flow.</p>
<p>The 'flow-into' property does not affect the CSS cascade and inheritance for
- the elements on which it is specified. The flow property affects the visual
- formatting of elements associated to a named flow and of regions getting
- their content from a named flow.</p>
-
- <p>The containing block for absolutely positioned descendants of an element
- with a specified flow is the region into which the element is rendered.</p>
-
- <p>The elements flowed inside the same named flow are taken in document order.</p>
-
- <p><span title="region">Regions</span> create a new stacking context.</p>
-
- <p>
- Floats or other exclusions (see [[CSS3EXCLUSIONS]]) potentially impact the
- content laid out in regions, just as for non-regions.</p>
-
- <div class="note">
- <p>This note is informative.</p>
- <p>With regions, an element may be split across multiple regions and these
- regions may overlap (for example if they are absolutely positioned).
- So fragments of the same element can overlap each other.
- Since each element has a single z-index, it would be required to
- find another mechanism to decide in which order the
- fragments are rendered. Since each region creates a new stacking
- context, it is clear that each region is rendered separately and their
- rendering order follows the regular CSS rendering model.
- </p>
- </div>
-
- <div class="example">
- <p>In the following example, the inline content coming from the
- <code class="html">body_text</code> <span title="named-flow">named
- flow</span> wraps around the <code class="html">#float</code> box.</p>
- <pre>
- <style>
- #float {
- float: left;
- width: 100px;
- height: 300px;
- }
-
- #region1, #region2 {
- width: 200px;
- height: 200px;
- content: flow-from(body_text);
- }
-
- #content {
- flow-into: body_text;
- }
- </style>
-
- <div id="float"></div>
+ the elements on which it is specified. The 'flow-into' property affects the visual
+ formatting of elements placed into a named flow and of regions laying out
+ content from a named flow.</p>
- <div id="region1"></div>
- <div id="region2"></div>
+ <p>The edges of the first region in a region chain associated with a named flow establish
+ the rectangle that is the initial containing block of the named flow.</p>
- <div id="content"></div>
- </pre>
- </div>
+ <p>Elements in a named flow are sequenced in document order.</p>
<div class="note">
- <p>This note is informative.</p>
- <p>It is important to understand that the 'flow-into' property moves an
- element into the flow and the interplay with selectors should be understood.
- For example, </p>
+ <p><em>This note is informative.</em></p>
+ <p>The 'flow-into' property moves an
+ element into the flow and the interplay with selectors should be considered carefully.</p>
+ <p>For example, </p>
<pre>table {flow-into: table-content}</pre>
<p>will
move all tables in the 'table-content' named flow. However, the</p>
@@ -665,29 +605,34 @@
<p>
- If ‘flow’ property is specified on an
+ If the ‘flow-into’ property is specified on an
<code class=
"html"><iframe></code>, an <code class=
"html"><object></code> or a <code class=
"html"><embed></code> element, the
‘display’ property is computed to ‘none’ and the referenced document within the element is used as the named flow.
- In the case of the object element if fallback occurs and the fallback element has a referenced document then that
+ In the case of the <code class="html"><object></code> element if fallback occurs and the fallback element has a referenced document then that
document is used as the named flow, otherwise the fallback element itself is added to the named flow.
</p>
<p>
- Any properties set on the iframe/object/embed elements (including margin, border, padding, background) have no effect.
- This redirection of content does not change representation of the elements in document tree, just as for any other
- source of named flow; in this case iframe still provides security checks for script in content (and sandbox if required),
- events and CSS cascading work the same way as in a documents hosted in regular iframes.
+ Any properties set on the <code class=
+ "html"><iframe></code>/<code class=
+ "html"><object></code>/<code class=
+ "html"><embed></code> elements (including margin, border, padding, background) have no effect.
+ This redirection of content does not change representation of the elements in the document tree, just as for any other
+ source of named flow; in this case the <code class="html"><iframe></code> still provides security checks for script in content (and sandbox if required).
+ Events and CSS cascading work the same way as in a documents hosted in regular <code class="html"><iframe></code>s.
</p>
<p>
- Region styling applies to content coming from iframe/object/embed sources exactly the same way as to any other flow content.
+ Region styling applies to content coming from <code class=
+ "html"><iframe></code>/<code class=
+ "html"><object></code>/<code class=
+ "html"><embed></code> sources the same way it applies to other flow content.
</p>
<h3 id="the-content-property">The 'content' property</h3>
- <p>This specification extends the definition of the 'content' property and
- makes it applicable to all block elements and pseudo-elements.</p>
+ <p>This specification extends the definition of the 'content' property.</p>
<table class="propdef" summary="content property definition">
<tr>
@@ -811,15 +756,15 @@
<dt><dfn id="flow-from-name">flow-from(<ident>)</dfn></dt>
- <dd>The element will visually format the available elements in the
- named flow with name <a href="http://www.w3.org/TR/2011/REC-CSS2-20110607/syndata.html#value-def-identifier"><ident></a>. If there is no flow with name
- <ident>, then the element is disconnected and does not format
- any children visually. Multiple elements may be associated with the
- same named flow. See the 'content-order' property description to
- understand how content segments are associated with different
- regions.
+ <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
+ <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 />
- 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'. This might be expanded in future versions of the specification
+ This might be expanded in future versions of the specification
to allow other types of containers to receive flow content.
</dd>
</dl>
@@ -829,6 +774,7 @@
referenced by one or more regions.</p>
<div class="note">
+ <p><em>This note is informative.</em></p>
<p>The 'content' property applies to block-level elements and the
'::before' and '::after' pseudo elements. User agents may apply the
content property to inline elements. The behavior is undefined in that
@@ -851,7 +797,11 @@
<p>See <a href="http://wiki.csswg.org/spec/css3-regions#contentflow-flow-from-name-vs-flow-fromflow-name">issue</a></p>
</div>
- <div class="issue">
+ <div class="issue stale">
+
+ <p>NOTE: stale issue because the spec. now contains a way to address these
+ requirements.</p>
+
<p>Should we consider adding the ability to do the following:</p>
<ul>
@@ -914,6 +864,58 @@
questions regarding DOM access, CSSOM view and the computed style.</p>
</div>
+ <p><span title="region">Regions</span> create a new stacking context.</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
+ regions may overlap (for example if they are absolutely positioned).
+ So fragments of the same element can overlap each other.
+ Since each element has a single z-index, it would be required to
+ find another mechanism to decide in which order the
+ fragments are rendered. Since each region creates a new stacking
+ context, it is clear that each region is rendered separately and their
+ rendering order follows the regular CSS rendering model.
+ </p>
+ </div>
+
+ <p>
+ Floats or other exclusions (see [[CSS3EXCLUSIONS]]) potentially impact the
+ content laid out in regions, just as for non-regions.</p>
+
+
+ <div class="example">
+ <p>In the following example, the inline content coming from the
+ <code class="html">body_text</code> <span title="named-flow">named
+ flow</span> wraps around the <code class="html">#float</code> box.</p>
+ <pre>
+ <style>
+ #float {
+ float: left;
+ width: 100px;
+ height: 300px;
+ }
+
+ #region1, #region2 {
+ width: 200px;
+ height: 200px;
+ content: flow-from(body_text);
+ }
+
+ #content {
+ flow-into: body_text;
+ }
+ </style>
+
+ <div id="float"></div>
+
+ <div id="region1"></div>
+ <div id="region2"></div>
+
+ <div id="content"></div>
+ </pre>
+ </div>
+
<h3 id="the-content-order-property">The 'content-order' property</h3>
<p>Defines the ordering of the chain of regions into which content flows.
@@ -985,7 +987,10 @@
'content-order' value. If multiple regions in have the same 'content-order'
value, they are sorted according to the document order.</p>
- <div class="issue">
+ <div class="issue stale">
+ <p>The working group made that the first
+ version of Grid layout would not have pseudo-elements for grid cells,
+ making this issue stale.</p>
CSS Modules should define the document order for pseudo elements. For
example, the [CSSGRID] specification should define the document order
for the '::grid-cell' pseudo elements (e.g., row-major sorting or
@@ -996,7 +1001,7 @@
"region-flow-break-properties-break-before-break-after-break-inside">Region
flow break properties: 'break-before', 'break-after', 'break-inside'</h3>
- <p>When content is laid out in multiple regions, the user agent must
+ <p>User agents laying out content in multiple regions, the must
determine where content breaks occur. The problem of breaking content into
segments fitting in regions is similar to breaking content into pages or
columns.</p>
@@ -1230,6 +1235,7 @@
overflow. In that case the 'overflow' property specified on the region
element should be used to determine how to render the overflow.</p>
+<!--
<p>The following sections define where region breaks may happen when
positioning a named flow across <span title="region">regions</span> in a
@@ -1376,7 +1382,7 @@
block to the next region.</li>
</ul>
</div>
-
+-->
<h3 id="the-region-overflow-property">The region-overflow property</h3>
<table class="propdef" summary="break-after property definition">
@@ -1652,12 +1658,16 @@
formatted line definition in CSS</a> in [[!SELECT]]</p>
</div>
- <div class="issue">
+ <div class="issue stale">
+ <p>Making issue stale because this issue has not been raised on the
+ mailing list and we will wait for implementation feedback.</a>
+
Is the proposed restriction that elements are only selected selector in
a rule set appearing in an @region rule sufficient?
</div>
- <div class="issue">
+ <div class="issue moved">
+ <a href="http://wiki.csswg.org/spec/css3-regions?&#issue-14region-lines-pseudo-selector">Moved to specification Wiki</a>.
There is <a href=
"http://lists.w3.org/Archives/Public/www-style/2011May/0518.html">concern</a>
that the ''first-line'' precedent is underspecified and that more
@@ -1717,19 +1727,10 @@
content on a mobile phone with a small screen may require more regions than
on a large desktop display.</p>
- <p>Here is another example where creating more regions might be needed. If
+ <p>Another example where creating more regions might be needed: if
the user may change the font size of text flowing through regions, new
regions may be needed to accommodate for the additional space required to
- fit the larger text or some may need to be removed for smaller text.</p>
-
- <p>The CSS OM View ([[CSSOM-VIEW]]) specification defines extensions to the
- <code class="idl">Element</code> interface that would let an author find
- out if the last region overflows its content boundaries (by comparing its
- 'scrollHeight' with its 'contentHeight'). However, this assumes the region
- is a document element, which may not always be the case. For example, as
- described in a later section, a grid cell (see [[CSS3-GRID-LAYOUT]]) may be
- a region, but it is a pseudo-element, not an document element. Therefore,
- it is not possible to access its 'scrollHeight' or 'contentHeight'.</p>
+ fit the larger text or some regions may need to be removed for smaller text.</p>
<div class="note">
<p>Since an element may be split into multiple regions, invoking
@@ -1741,9 +1742,9 @@
<h3 id="the-namedflow-interface">The NamedFlow interface</h3>
- <p>This specification adds a method to the <a href=
+ <p>The <code class="idl">getFlowByName</code method on the <a href=
"http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document"><code class=
- "idl">Document</code></a> interface to access the document's <span title=
+ "idl">Document</code></a> interface provides access to the document's <span title=
"named-flow">named flow</span> instances.</p>
<pre class="idl">
[Supplemental] interface <a href=
@@ -1770,7 +1771,7 @@
<p>With the <a href="#dom-namedflow"><code class="idl">NamedFlow</code></a>
interface, authors can easily check if all content has been fitted into
- existing regions. If it has, the overflow property would be true.</p>
+ existing regions. If it has, the overflow property would be false.</p>
<h3 id="extension-to-the-element-interface">Extension to the Element
interface</h3>
@@ -1820,7 +1821,7 @@
content is further fitted in subsequent regions. In particular, in this
last case, that means the region may have received no content from the
<span title="named-flow">named flow</span> (for example if the region
- is too span to accommodate any content).</dd>
+ is too small to accommodate any content).</dd>
<dt>'empty'</dt>
@@ -1849,11 +1850,7 @@
<div class="note">
The Element interface extension is only available to regions that are
- document elements and not to regions that are pseudo-elements. For
- example, when regions are created with a grid layout, this interface
- cannot be used because the regions are not document elements but
- pseudo-elements. In that situation, the NamedFlow interface can be
- used.
+ document elements and not to regions that are pseudo-elements.
</div>
<div class="issue resolved">
@@ -1890,6 +1887,7 @@
</tbody></table>
+<!--
<h2 id="integration-with-other-specifications">Integration with other
specifications</h2>
@@ -1976,7 +1974,7 @@
<p>The CSS Multi-Column Layout (see [[CSS3COL]]) does not specify a
selector for column boxes. Therefore, column boxes cannot be regions.</p>
-
+-->
<!--
<p> </p>
@@ -2016,7 +2014,7 @@
regular 'column-flow' would thread through the first and third column while
column two would flow content from the 'illustration' named flow.</p>
-->
-
+<!--
<h4 id="css-visual-formatting">CSS Visual Formatting</h4>
<p>CSS (see [[CSS21]]) offers a way to visually format content with
@@ -2057,7 +2055,7 @@
</pre>
</div>
-
+-->
<h2 id="relation-to-other-specifications">Relation to other
specifications</h2>
@@ -2072,7 +2070,7 @@
extension to the way CSS floats provide rectangular areas into which
content flows and around which content flows. In advanced layout
designs, it is expected that the CSS Exclusions module will be commonly
- combined with the CSS Regions module.</li>
+ combined with the CSS regions module.</li>
<li>CSS Line Grid Module [[CSS3LINEGRID]]. This module defines a
concept of line grid to align the position of lines in different
@@ -2087,6 +2085,7 @@
<h3 id="changes_from_June_09_2011">Changes from <a href="http://www.w3.org/TR/2011/WD-css3-regions-20110609/">June 09<sup>th</sup> 2011</a> version</h3>
<ul>
+ <li>Editorial changes (typos, rephrasings).</li>
<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>
@@ -2141,10 +2140,10 @@
block as agreed on <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0161.html">mailing list discussion</a>.</li>
<li>Reworded the paragraph on how regions create a new stacking context, as
per the <a href="http://lists.w3.org/Archives/Public/www-style/2011Aug/0025.html">mailing list discussion</a></li>.
- <li>Reworked the "CSS Regions Model" section to now be "CSS Regions Layout". Moved the
+ <li>Reworked the "CSS regions Model" section to now be "CSS regions Layout". Moved the
definition of a region as the first sub-section.</li>
<li>Removed the "Visual Formatting Model and Flows" section to match the new Regions Model
- (now CSS Regions Layout) section.</li>
+ (now CSS regions Layout) section.</li>
<li>Moved the sections on allowed region breaks, forced region breaks and "best" regions
breaks to follow the property definitions to follow the formatting of the paged
media section in CSS 2.1.</li>
@@ -2157,6 +2156,12 @@
<li>Added the ::region-before and a ::region-after pseudo-elements.</li>
<li>Added note of caution when using selectors and the 'flow-into' property following
a <a href="http://lists.w3.org/Archives/Public/www-style/2011Jul/0191.html">mailing list discussion</a>.</li>
+ <li>Removed sections about allowed, forced and best region breaks to align with the
+ multi-column specification approach and until the group agrees on where and how the
+ general issue of breaks (regions/pages/columns) should be addressed.</li>
+ <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>
</ul>
<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
Received on Friday, 12 August 2011 00:10:31 UTC