W3C home > Mailing lists > Public > public-css-commits@w3.org > July 2011

csswg/css3-regions Overview.html,1.12,1.13 Overview.src.html,1.10,1.11

From: Vincent Hardy via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 13 Jul 2011 20:41:50 +0000
To: public-css-commits@w3.org
Message-Id: <E1Qh6Fi-0002wc-JB@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-regions
In directory hutz:/tmp/cvs-serv11304

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Updated following discussion with Alex

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -d -r1.12 -r1.13
--- Overview.html	13 Jul 2011 17:25:06 -0000	1.12
+++ Overview.html	13 Jul 2011 20:41:48 -0000	1.13
@@ -542,6 +542,11 @@
   <p>A <span title=region>region</span>&lsquo;<code class=css>s intrinsic
    width is zero.</code>
 
+  <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>
+
   <h3 id=flow-breaking-rules><span class=secno>2.3. </span>Flow breaking
    rules</h3>
 
@@ -920,7 +925,8 @@
    <dd>The element is placed (appended) to the flow with that name. The
     element is said to have a <dfn id=specified-flow>specified flow</dfn>.
     The values &lsquo;<code class=property>none</code>&rsquo;, &lsquo;<code
-    class=property>inherit</code>&rsquo; and &lsquo;<code
+    class=property>inherit</code>&rsquo;, &lsquo;<code
+    class=property>default</code>&rsquo; and &lsquo;<code
     class=property>initial</code>&rsquo; and invalid flow names.
   </dl>
 
@@ -1171,6 +1177,18 @@
   </div>
 
   <div class=issue>
+   <p><strong>content: from-flow(&lt;low-name&gt;) v.s. from-flow:
+    &lt;flow-name&gt;</strong></p>
+
+   <p><a
+    href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">WG
+    Conference Call, CSSWG Minutes and Resolutions 2011-06-15</a>.</p>
+
+   <p>See <a
+    href="http://wiki.csswg.org/spec/css3-regions#contentfrom-flow-flow-name-vs-from-flowflow-name">issue</a></p>
+  </div>
+
+  <div class=issue>
    <p>Should we consider adding the ability to do the following:</p>
 
    <ul>
@@ -1591,7 +1609,8 @@
    <dd>Content flows as it would in a regular content element. If the content
     exceeds the container box, it is subject to the <a
     href="http://www.w3.org/TR/CSS21/visufx.html#propdef-overflow">overflow</a>
-    property's computed value on the region element.
+    property's computed value on the region element. Region breaks must be
+    ignored on the last region.
 
    <dt>break
 
@@ -1599,7 +1618,8 @@
     property has no effect. If the content does not fit within the <em>region
     element</em>, the content breaks as if flow was going to continue in a
     subsequent region. See the <a href="#breaking-rules">breaking rules</a>
-    section.
+    section. A forced region break takes precedence over a natural break
+    point.
   </dl>
 
   <p>The following code sample illustrates the usage of the &lsquo;<a
@@ -1893,7 +1913,7 @@
 
   <pre class=idl>
 [Supplemental] interface <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document">Document</a> {
-  <a href="#dom-namedflow">NamedFlow</a> <a href="#dom-document-flowwithname">flowWithName(</a><a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMString">DOMString</a> name);
+  <a href="#dom-namedflow">NamedFlow</a> <a href="#dom-document-getflowbyname">getFlowByName(</a><a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMString">DOMString</a> name);
 };               
 </pre>
 
@@ -1909,7 +1929,8 @@
 
   <p>The <dfn id=dom-namedflow-overflow><code class=idl>overflow</code></dfn>
    property is true if the named flow does not fully fit in the associated
-   regions. Otherwise, it is false.
+   regions. Otherwise, it is false. A <a href="#dom-namedflow"><code
+   class=idl>NamedFlow</code></a> object is live.
 
   <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
@@ -1928,7 +1949,7 @@
   <pre class=idl>
 [Supplemental] interface <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-745549614">Element</a> {
     readonly attribute <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMString">DOMString</a> <a href="#dom-element-regionoverflow">regionOverflow</a>;
-    readonly <a href="#">Range</a>[] <a href="#dom-element-flowranges">flowRanges</a>;
+    getter <a href="#">Range</a>[] <a href="#dom-element-getregionflowranges">getRegionFlowRanges</a>;
 };               
     
 </pre>
@@ -1938,7 +1959,8 @@
    following values:
 
   <dl>
-   <dt>overflow
+   <dt>&lsquo;<a href="#dom-namedflow-overflow"><code
+    class=property>overflow</code></a>&rsquo;
 
    <dd>the region element's content overflows the region's <a
     href="http://www.w3.org/TR/CSS21/box.html#box-dimensions">content
@@ -1950,7 +1972,7 @@
     to fit the remaining content from the <span title=named-flow>named
     flow</span>.
 
-   <dt>fit
+   <dt>&lsquo;<code class=property>fit</code>&rsquo;
 
    <dd>the region element's content fits into the region's <a
     href="http://www.w3.org/TR/CSS21/box.html#box-dimensions">content
@@ -1963,31 +1985,34 @@
     title=named-flow>named flow</span> (for example if the region is too span
     to accommodate any content).
 
-   <dt>empty
+   <dt>&lsquo;<code class=property>empty</code>&rsquo;
 
    <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 &lsquo;<a href="#content-order"><code
     class=property>content-order</code></a>&rsquo; value.
-  </dl>
 
-  <p>If an element is not a <span>region</span>, then the <code
-   class=idl>contentOverflow</code> attribute value is &lsquo;<code
-   class=property>fit</code>&rsquo;.
+   <dt>&lsquo;<code class=property>undefined</code>&rsquo;
+
+   <dd>The element is not a <span>region</span>.
+  </dl>
 
   <p>&nbsp;
 
-  <p>The <dfn id=dom-element-flowranges>flowRanges</dfn> attribute is an
-   array of <a
+  <p>The <dfn id=dom-element-getregionflowranges>getRegionFlowRanges</dfn>
+   method returns an array of <a
    href="http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-idl">
    Range</a> instances corresponding to the content from the region flow that
    is positioned in the region.
 
-  <p>If an element is not an <span>region</span>, then the <a
-   href="#dom-element-flowranges"><code class=idl><span
-   title="#document-element-flowranges">flowRanges</span></code></a>
-   attribute returns an array with a single <code class=idl><span
-   title=range>Range</span></code> matching the element's full content.
+  <p>If an element is not a <span>region</span>, the <a
+   href="#dom-element-getregionflowranges"><code class=idl><span
+   title="#document-element-getregionflowranges">getRegionFlowRanges</span></code></a>
+   method throws a <a
+   href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187"><code
+   class=idl>DOMException</code></a> with the <a
+   href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMException-INVALID_ACCESS_ERR"><code
+   class=idl>INVALID_ACCESS_ERR</code></a> error code.
 
   <div class=note> The Element interface extension is only available to
    regions that are document elements and not to regions that are
@@ -2009,7 +2034,7 @@
 
   <p>Region <a
    href="http://www.w3.org/TR/DOM-Level-3-Events/#glossary-event">Event
-   Targets</a> dispatch <code class=idl>NamedFlowEvent</code>s when there is
+   Targets</a> dispatch <code class=idl>NamedFlowUpdate</code>s when there is
    a possible layout change of their named flow segment.
 
   <table border=0 cellpadding=2 cellspacing=0 class=event-desc summary="This
@@ -2018,7 +2043,7 @@
     <tr class="assert must">
      <th>Type
 
-     <td class=eventname><strong><code>NamedFlowEvent</code></strong>
+     <td class=eventname><strong><code>NamedFlowUpdate</code></strong>
 
     <tr class="assert must">
      <th>Interface
@@ -2279,7 +2304,7 @@
       into a note explaining that the NamedFlow interface can be used when
       regions are pseudo-elements.
 
-     <li>Added NamedFlowEvent
+     <li>Added NamedFlowUpdate
     </ul>
 
    <li>Excluded &lsquo;<code class=property>none</code>&rsquo;, &lsquo;<code
@@ -2296,6 +2321,30 @@
    <li>Added specification of how the &lsquo;<a href="#flow2"><code
     class=property>flow</code></a>&rsquo; property interacts with object,
     embed and iframe elements.
+
+   <li>Excluded &lsquo;<code class=property>default</code>&rsquo; from the
+    possible identifier names on the flow property because it <a
+    href="http://www.w3.org/TR/2006/WD-css3-values-20060919/#keywords">may
+    get reserved</a>.
+
+   <li>Added to the definition of &lsquo;<code
+    class=property>auto</code>&rsquo; on &lsquo;<a
+    href="#region-overflow"><code
+    class=property>region-overflow</code></a>&rsquo; specifying that region
+    breaks must be ignored.
+
+   <li>Renamed &lsquo;<code class=css>Document.flowWithName</code>&rsquo; to
+    &lsquo;<code class=css>Document.getFlowByName</code>&rsquo; since it is
+    not a property.
+
+   <li>Added a note that a &lsquo;<a href="#dom-namedflow"><code
+    class=property>NamedFlow</code></a>&rsquo; instance is live.
+
+   <li>Added an &lsquo;<code class=property>undefined</code>&rsquo; string
+    value to the regionOverflow property on the Element interface extension.
+
+   <li>Renamed NamedFlowEvent to NamedFlowUpdate to avoid having &lsquo;<code
+    class=property>Event</code>&rsquo; in the event name.
   </ul>
 
   <h2 class=no-num id=acknowledgments>Acknowledgments</h2>
@@ -2465,15 +2514,15 @@
 
    <li>flow, <a href="#flow2" title=flow><strong>3.1.</strong></a>
 
-   <li>flowRanges, <a href="#dom-element-flowranges"
-    title=flowRanges><strong>4.2.</strong></a>
-
    <li>from-flow(&lt;ident&gt;), <a href="#from-flow-name"
     title="from-flow(&lt;ident&gt;)"><strong>3.2.</strong></a>
 
    <li>generated flow, <a href="#generated-flow-def" title="generated
     flow"><strong>2.4.4.</strong></a>
 
+   <li>getRegionFlowRanges, <a href="#dom-element-getregionflowranges"
+    title=getRegionFlowRanges><strong>4.2.</strong></a>
+
    <li>grid cell flow, <a href="#grid-cell-flow" title="grid cell
     flow"><strong>2.4.3.</strong></a>
 

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-regions/Overview.src.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- Overview.src.html	13 Jul 2011 15:57:41 -0000	1.10
+++ Overview.src.html	13 Jul 2011 20:41:48 -0000	1.11
@@ -356,6 +356,11 @@
     property).</p>
 
     <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>
 
     <h3 id="flow-breaking-rules">Flow breaking rules</h3>
 
@@ -689,7 +694,7 @@
 
         <dd>The element is placed (appended) to the flow with that name. The
         element is said to have a <dfn id="specified-flow">specified
-        flow</dfn>. The values 'none', 'inherit' and 'initial' and invalid flow
+        flow</dfn>. The values 'none', 'inherit', 'default' and 'initial' and invalid flow
         names.</dd>
     </dl>
 
@@ -925,6 +930,13 @@
     </div>
 
     <div class="issue">
+        <p><strong>content: from-flow(&lt;low-name&gt;) v.s. from-flow: &lt;flow-name&gt;</strong></p>
+
+        <p><a href="http://lists.w3.org/Archives/Public/www-style/2011Jun/0413.html">WG Conference Call, CSSWG Minutes and Resolutions 2011-06-15</a>.</p>
+        
+        <p>See <a href="http://wiki.csswg.org/spec/css3-regions#contentfrom-flow-flow-name-vs-from-flowflow-name">issue</a></p>
+    </div>
+    <div class="issue">
         <p>Should we consider adding the ability to do the following:</p>
 
         <ul>
@@ -1362,7 +1374,8 @@
         <dd>Content flows as it would in a regular content element. If the
         content exceeds the container box, it is subject to the <a href=
         "http://www.w3.org/TR/CSS21/visufx.html#propdef-overflow">overflow</a>
-        property's computed value on the region element.</dd>
+        property's computed value on the region element. Region breaks must be 
+        ignored on the last region.</dd>
 
         <dt>break</dt>
 
@@ -1370,7 +1383,8 @@
         property has no effect. If the content does not fit within the
         <em>region element</em>, the content breaks as if flow was going to
         continue in a subsequent region. See the <a href=
-        "#breaking-rules">breaking rules</a> section.</dd>
+        "#breaking-rules">breaking rules</a> section. A forced region break takes precedence over
+        a natural break point.</dd>
     </dl>
 
     <p>The following code sample illustrates the usage of the 'region-overflow'
@@ -1641,7 +1655,7 @@
 [Supplemental] interface <a href=
 "http://www.w3.org/TR/DOM-Level-3-Core/core.html#i-Document">Document</a> {
   <a href="#dom-namedflow">NamedFlow</a> <a href=
-"#dom-document-flowwithname">flowWithName(</a><a href=
+"#dom-document-getflowbyname">getFlowByName(</a><a href=
 "http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMString">DOMString</a> name);
 };               
 </pre>
@@ -1657,7 +1671,8 @@
 
     <p>The <dfn id="dom-namedflow-overflow"><code class=
     "idl">overflow</code></dfn> property is true if the named flow does not
-    fully fit in the associated regions. Otherwise, it is false.</p>
+    fully fit in the associated regions. Otherwise, it is false. A 
+    <code class="idl">NamedFlow</code> object is live.</p>
 
     <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
@@ -1677,8 +1692,8 @@
 "http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-745549614">Element</a> {
     readonly attribute <a href=
 "http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMString">DOMString</a> <a href="#dom-element-regionoverflow">regionOverflow</a>;
-    readonly <a href="#">Range</a>[] <a href=
-"#dom-element-flowranges">flowRanges</a>;
+    getter <a href="#">Range</a>[] <a href=
+"#dom-element-getregionflowranges">getRegionFlowRanges</a>;
 };               
     
 </pre>
@@ -1688,7 +1703,7 @@
     values:</p>
 
     <dl>
-        <dt>overflow</dt>
+        <dt>'overflow'</dt>
 
         <dd>the region element's content overflows the region's <a href=
         "http://www.w3.org/TR/CSS21/box.html#box-dimensions">content box</a>.
@@ -1700,7 +1715,7 @@
         not able to fit the remaining content from the <span title=
         "named-flow">named flow</span>.</dd>
 
-        <dt>fit</dt>
+        <dt>'fit'</dt>
 
         <dd>the region element's content fits into the region's <a href=
         "http://www.w3.org/TR/CSS21/box.html#box-dimensions">content box</a>.
@@ -1713,28 +1728,30 @@
         <span title="named-flow">named flow</span> (for example if the region
         is too span to accommodate any content).</dd>
 
-        <dt>empty</dt>
+        <dt>'empty'</dt>
 
         <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>
+        
+        <dt>'undefined'</dt>
+        <dd>The element is not a <span>region</span>.</dd>
     </dl>
 
-    <p>If an element is not a <span>region</span>, then the <code class=
-    "idl">contentOverflow</code> attribute value is 'fit'.</p>
+
 
     <p>&nbsp;</p>
 
-    <p>The <dfn id="dom-element-flowranges">flowRanges</dfn> attribute is an
-    array of <a href=
+    <p>The <dfn id="dom-element-getregionflowranges">getRegionFlowRanges</dfn> method returns
+    an array of <a href=
     "http://www.w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html#Level-2-Range-idl">
     Range</a> instances corresponding to the content from the region flow that
     is positioned in the region.</p>
 
-    <p>If an element is not an <span>region</span>, then the <code class=
-    "idl"><span title="#document-element-flowranges">flowRanges</span></code>
-    attribute returns an array with a single <code class="idl"><span title=
-    "range">Range</span></code> matching the element's full content.</p>
+    <p>If an element is not a <span>region</span>, the <code class=
+    "idl"><span title="#document-element-getregionflowranges">getRegionFlowRanges</span></code>
+    method throws a <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-17189187"><code class="idl">DOMException</code></a> with the 
+    <a href="http://www.w3.org/TR/DOM-Level-3-Core/core.html#DOMException-INVALID_ACCESS_ERR"><code class="idl">INVALID_ACCESS_ERR</code></a> error code.</p>
 
     <div class="note">
         The Element interface extension is only available to regions that are
@@ -1756,12 +1773,12 @@
     <h3 id="region-flow-layout-events">Region Flow Layout Events</h3>
     
     <p>Region <a href="http://www.w3.org/TR/DOM-Level-3-Events/#glossary-event">Event Targets</a> 
-    dispatch <code class="idl">NamedFlowEvent</code>s when there is a possible layout change of their named flow 
+    dispatch <code class="idl">NamedFlowUpdate</code>s when there is a possible layout change of their named flow 
     segment.</p>
     
     <table class="event-desc" border="0" summary="This table contains information about the semantics of the given event type" cellpadding="2" cellspacing="0">
                 <tbody><tr class="assert must"><th>Type</th>
-                <td class="eventname"><strong><code>NamedFlowEvent</code></strong></td></tr>
+                <td class="eventname"><strong><code>NamedFlowUpdate</code></strong></td></tr>
                 <tr class="assert must"><th>Interface</th> <td><a href="#events-UIEvent"><code>UIEvent</code></a></td></tr>
                 <tr class="assert must"><th>Sync / Async</th> <td>Sync</td></tr>
                 <tr class="assert must"><th>Bubbles</th> <td>Yes</td></tr>
@@ -1975,7 +1992,7 @@
         	<ul>
             	<li>Turned the first issue in the "Extensions to the Element interface" into a note 
             explaining that the NamedFlow interface can be used when regions are pseudo-elements.</li>
-            	<li>Added NamedFlowEvent</li>
+            	<li>Added NamedFlowUpdate</li>
                 </ul>
         </li>
         <li>Excluded 'none', 'inherit' and 'initial' from the possible identifier names on 
@@ -1984,6 +2001,15 @@
         column boxes are not addressable by selectors, they cannot be regions.</li>
         <li>Added specification of how the 'flow' property interacts with object, embed and iframe 
         elements.</li>
+        <li>Excluded 'default' from the possible identifier names on the flow property because it 
+            <a href="http://www.w3.org/TR/2006/WD-css3-values-20060919/#keywords">may get reserved</a>.</li>
+        <li>Added to the definition of 'auto' on 'region-overflow' specifying that region breaks must
+            be ignored.</li>
+        <li>Renamed 'Document.flowWithName' to 'Document.getFlowByName' since it is not a property.</li>
+        <li>Added a note that a 'NamedFlow' instance is live.</li>
+        <li>Added an 'undefined' string value to the regionOverflow property on the Element interface 
+            extension.</li>
+        <li>Renamed NamedFlowEvent to NamedFlowUpdate to avoid having 'Event' in the event name.</li>
     </ul>
     
     <h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
Received on Wednesday, 13 July 2011 20:41:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 July 2011 20:41:58 GMT