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

csswg/css3-gcpm Overview.src.html,1.168,1.169

From: (wrong string) åkon Wium Lie via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 14 Nov 2011 23:41:58 +0000
To: public-css-commits@w3.org
Message-Id: <E1RQ6A2-0005y5-9F@lionel-hutz.w3.org>
Update of /sources/public/csswg/css3-gcpm
In directory hutz:/tmp/cvs-serv22927

Modified Files:
	Overview.src.html 
Log Message:
revising draft based on changes discussed at the Moutain View F2F; removing hyphenation, new list-styles

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-gcpm/Overview.src.html,v
retrieving revision 1.168
retrieving revision 1.169
diff -u -d -r1.168 -r1.169
--- Overview.src.html	1 Nov 2011 19:15:03 -0000	1.168
+++ Overview.src.html	14 Nov 2011 23:41:55 -0000	1.169
@@ -72,7 +72,13 @@
 
 <!--end-status-->
 
-<p>This functionality described in this WD is scaled down compared to earlier versions. The remaining functionality is considered to be useful, to fit well into the CSS framework, and to be within reach of implementations. Indeed, significant parts of the draft has already been implemented. 
+<p>This WD contains functionality that the CSS WG finds interesting
+and useful. In general, the earlier a feature appears in this draft,
+the more stable it is. Significant changes in functionality and syntax
+must be expected from <a href="#paged-presentations">paged
+presentations</a> and onwards. Also, functionality described in this
+module may be moved to other modules. Since the previous WD,
+hyphenation and new list style type have been moved.
 
 
 <h2 class="no-num no-toc"><a name="contents">Table of contents</a></h2>
@@ -528,6 +534,11 @@
 <p>The second value describes the alignment of the leader. These values are allowed:
 
 <dl>
+
+<dt>align
+
+<dd>attempt to align corresponding glyphs from the  leader pattern between consecutive lines. This is the default value.
+
 <dt>start
 <dd>align leader string with the start
 
@@ -541,27 +552,22 @@
 <dd>add space between strings to take up all available space
 
 <dt>letter-space
-<dd>space out letters to take up all available space
-
-<dt>align
-<dd>attempt to align corresponding glyphs from the  
-leader pattern between consecutive lines
+<dd>add space between letters (both inside the string, and at the start/end of the string) to take up all available space
 
 </dl>
 
 <div class=example>
 <pre>
+heading::after { content: leader(dotted, align) }
 heading::after { content: leader(dotted, start) }
 heading::after { content: leader(dotted, end) }
 heading::after { content: leader(dotted, center) }
-heading::after { content: leader(dotted, space) }
-heading::after { content: leader(dotted, pattern) }
+heading::after { content: leader(dotted, string-space) }
+heading::after { content: leader(dotted, letter-space) }
 </pre>
 </div>
 
 
-
-
 <p>In a more complex example, the 'leader' value is combined with other
 values on the 'content' property:
 
@@ -792,7 +798,7 @@
 <li>one predefined counter: ''footnote''
 <li>one new value on the 'content' property: ''target-pull()''
 <li>border segments
-<li>two new 'list-style-type' values: ''super-decimal'', and symbol(...)
+<!--<li>two new 'list-style-type' values: ''super-decimal'', and symbol(...)-->
 </ul>
 
 
@@ -1590,6 +1596,7 @@
 </div>
 -->
 
+<!--
 <h2>New counter styles</h2>
 
 
@@ -1617,8 +1624,8 @@
 <p>Using super-script glyphs is optional; UAs may also scale and position
 other glyphs for use in footnote calls.
 
-
-
+-->
+<!--
 <h3>Named counter styles</h3>
 
 <p>CSS defines a number of predefined list style types for the
@@ -1643,7 +1650,6 @@
 
 </div>
 
-
 <div class="example">
 
 <pre>
@@ -1682,6 +1688,7 @@
 ol { list-style-type: armenian }
 </pre>
 </div>
+-->
 
 <!--
 <div class="issue">Should we allow images in addition to strings? 
@@ -1690,7 +1697,7 @@
 </pre>
 </div>
 -->
-
+<!--
 <h3>The ''symbols()'' list-style-type</h3>
 
 <p>A new list-style-type with a functional notation is introduced to
@@ -1721,7 +1728,7 @@
 will result in these list-items markers: * &#x2020; &#x2021; &#xA7; # 6 7 8 ...
 
 </div>
-
+-->
 <!--
 <p class="issue">Should there be a way to indicate the behavior if there are more items than strings? Proposals include: "alphabetic", "enumerate", "numeric", "cycle", "ideographic".
 -->
@@ -2158,7 +2165,7 @@
       <td><dfn>bookmark-label</dfn>
     <tr>
       <td><em>Value:</em>
-      <td>content() | attr() | &lt;string>
+      <td>content() |  &lt;string>
     <tr>
       <td><em>Initial:</em>
       <td>content()
@@ -2197,7 +2204,7 @@
       <td><dfn>bookmark-target</dfn>
     <tr>
       <td><em>Value:</em>
-      <td>none | &lt;uri> | &lt;attr>
+      <td>none | &lt;uri> 
     <tr>
       <td><em>Initial:</em>
       <td>none
@@ -2215,7 +2222,7 @@
       <td>all
     <tr>
       <td><em>Computed&nbsp;value:</em>
-      <td>For URI values, the absolute URI; for attr() values, the resulting URI or string; for other keywords, as specified.
+      <td>For URI values, the absolute URI; for 'none', as specified.
 </table>
 
 <p>This property specifies the target of the bookmark link. 
@@ -2359,7 +2366,7 @@
 
 <p>Printed publications are paged, while screen-based presentations of web pages are most often presented in a continous manner with a scrollbar on the side. There are reasons to believe that screen-based presentations also could benefit from using paged presentations. There is nothing in web specifications that prevent browsers from adding a page-based mode today. However, most web content is authored and styled with a continous presentation in mind. This could change if it becomes possible to describe paged presentations in style sheets. This section is an attempt to do so.
 
-<p>To support paged presentations, four new values are added to the 'overflow' property:
+<p>To support paged presentations, four new values are added to the 'overflow-style' property:
 
 <dl>
 <dt>paged-x
@@ -2381,7 +2388,9 @@
 </dl>
 
 <p class=issue>Is "paginated" a better word?
-<p class=issue>Should controls be specified on a separate property?
+<p class=issue>Should controls be specified on a separate property, or on an attribute (like HTML's video element)?
+<p class=issue>Should the axis (x/y) be specified on a separate property?
+
 
 <div class=example>
 <p>In this example, the root element is constrained to have the same
@@ -2392,7 +2401,7 @@
 
 <pre>
   html { 
-    overflow: paged-x;
+    overflow-style: paged-x;
     height: 100%;
   }
 </pre>
@@ -2406,7 +2415,7 @@
 
 <pre>
   #content { 
-    overflow: paged-x-controls;
+    overflow-style: paged-x-controls;
     height: 400px;
   }
 </pre>
Received on Monday, 14 November 2011 23:41:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 November 2011 23:42:01 GMT