csswg/css3-values Overview.html,1.86,1.87 Overview.src.html,1.89,1.90

Update of /sources/public/csswg/css3-values
In directory hutz:/tmp/cvs-serv9006

Modified Files:
	Overview.html Overview.src.html 
Log Message:
Add issue about cascade rollback; editorial tweaks to common keywords section

Index: Overview.html
===================================================================
RCS file: /sources/public/csswg/css3-values/Overview.html,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -d -r1.86 -r1.87
--- Overview.html	15 Aug 2011 23:09:04 -0000	1.86
+++ Overview.html	16 Aug 2011 18:37:15 -0000	1.87
@@ -29,13 +29,13 @@
 
    <h1 id=css3-template>CSS3 Values and Units</h1>
 
-   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 12 August 2011</h2>
+   <h2 class="no-num no-toc" id=longstatus-date>Editor's Draft 16 August 2011</h2>
 
    <dl>
     <dt>This version:
 
     <dd><a
-     href="http://www.w3.org/TR/2011/ED-css3-values-20110812/">http://www.w3.org/TR/2011/ED-css3-values-20110812/</a>
+     href="http://www.w3.org/TR/2011/ED-css3-values-20110816/">http://www.w3.org/TR/2011/ED-css3-values-20110816/</a>
 
     <dt>Latest version:
 
@@ -172,9 +172,9 @@
      <li><a href="#keywords"><span class=secno>3.1. </span> Pre-defined
       Keywords</a>
       <ul class=toc>
-       <li><a href="#initial-inherit"><span class=secno>3.1.1. </span> The
-        &lsquo;<code class=css>initial</code>&rsquo; and &lsquo;<code
-        class=css>inherit</code>&rsquo; keywords</a>
+       <li><a href="#common-keywords"><span class=secno>3.1.1. </span>
+        CSS-wide keywords: &lsquo;<code class=css>initial</code>&rsquo; and
+        &lsquo;<code class=css>inherit</code>&rsquo;</a>
       </ul>
 
      <li><a href="#identifiers"><span class=secno>3.2. </span> User-defined
@@ -570,14 +570,14 @@
    <pre>table { border-collapse: separate }</pre>
   </div>
 
-  <h4 id=initial-inherit><span class=secno>3.1.1. </span> The &lsquo;<code
-   class=css>initial</code>&rsquo; and &lsquo;<code
-   class=css>inherit</code>&rsquo; keywords</h4>
+  <h4 id=common-keywords><span class=secno>3.1.1. </span> CSS-wide keywords:
+   &lsquo;<code class=css>initial</code>&rsquo; and &lsquo;<code
+   class=css>inherit</code>&rsquo;</h4>
 
   <p>As defined <a href="#component-types">above</a>, all properties accept
    the &lsquo;<code class=css>initial</code>&rsquo; and &lsquo;<code
-   class=css>inherit</code>&rsquo; keywords, which represent value concepts
-   common to all CSS properties.
+   class=css>inherit</code>&rsquo; keywords, which represent value
+   computations common to all CSS properties.
 
   <p>The <dfn id=inherit>&lsquo;<code class=css>inherit</code>&rsquo;</dfn>
    keyword is <a
@@ -585,8 +585,8 @@
    in <a href="#CSS21" rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>.
 
   <p>The <dfn id=initial>&lsquo;<code class=css>initial</code>&rsquo;</dfn>
-   keyword represents the value that is designated as the property's initial
-   value. <a href="#CSS3CASCADE"
+   keyword represents the specified value that is designated as the
+   property's initial value. <a href="#CSS3CASCADE"
    rel=biblioentry>[CSS3CASCADE]<!--{{CSS3CASCADE}}--></a>
 
   <p class=issue>Should these keywords affect the specified or computed
@@ -596,9 +596,8 @@
    href="http://lists.w3.org/Archives/Public/www-style/2011May/0402.html">issues</a>.
    
 
-  <p class=issue>Would it be useful to have a &lsquo;<code
-   class=property>default</code>&rsquo; value, defined to be equivalent to <a
-   class=css href="#inherit">&lsquo;<code
+  <p class=issue>Would it be useful to have a value defined to be equivalent
+   to <a class=css href="#inherit">&lsquo;<code
    class=property>inherit</code>&rsquo;</a> for properties that are inherited
    by default and equivalent to <a class=css href="#initial">&lsquo;<code
    class=property>initial</code>&rsquo;</a> for properties that are not
@@ -610,6 +609,13 @@
    by default or not (which isn't obvious for some properties, such as
    text-decoration and visibility).
 
+  <p class=issue>It's been requested to have a value that rolls back to the
+   bottom of that level of the cascade, e.g. for an author rule it would roll
+   back to the end of the user cascade, for a user rule it would roll back to
+   the end of the UA cascade, and for the UA it would roll back to
+   &lsquo;<code class=css>initial</code>&rsquo;/&lsquo;<code
+   class=css>inherit</code>&rsquo;. Is that something we should add?
+
   <h3 id=identifiers><span class=secno>3.2. </span> User-defined Identifiers:
    the &lsquo;<a href="#identifier-value"><code
    class=css>&lt;identifier&gt;</code></a>&rsquo; type</h3>
@@ -1364,15 +1370,16 @@
    number. DIMENSION tokens have types of their units (&lsquo;<code
    class=property>cm</code>&rsquo; is length, &lsquo;<a href="#deg"><code
    class=property>deg</code></a>&rsquo; is angle etc.); any DIMENSION whose
-   type does not match the target type is not allowed and must be a parse
-   error. If percentages are accepted in that context and convertible to the
-   target type, a PERCENTAGE token in the expression has the target type;
-   otherwise percentages are not allowed and must be a parse error.
+   type does not match the target type causes the &lsquo;<a
+   href="#calc0"><code class=css>calc()</code></a>&rsquo; expression to be
+   invalid. If percentages are accepted in that context and convertible to
+   the target type, a PERCENTAGE token in the expression has the target type;
+   otherwise percentages are likewise invalid.
 
   <p>To make expressions simpler, operators have restrictions on the types
-   they accept. At each operator, the types of the left and right side have
-   to be checked for these restrictions. If compatible, they return roughly
-   as follows (the following ignores precedence rules on the operators for
+   they accept. At each operator, the types of the left and right side are be
+   checked for these restrictions. If compatible, they return roughly as
+   follows (the following ignores precedence rules on the operators for
    simplicity):
 
   <ol>
@@ -1412,10 +1419,9 @@
   <p>Given the complexities of &lsquo;<code
    class=property>width</code>&rsquo; and &lsquo;<code
    class=property>height</code>&rsquo; on table cells and table elements,
-   calc() expressions for &lsquo;<code class=property>width</code>&rsquo; and
-   &lsquo;<code class=property>height</code>&rsquo; on table columns, table
-   column groups, table rows, table row groups, and table cells in both auto
-   and fixed layout tables may be treated as if &lsquo;<code
+   calc() expressions for widths and heights on table columns, table column
+   groups, table rows, table row groups, and table cells in both auto and
+   fixed layout tables may be treated as if &lsquo;<code
    class=property>auto</code>&rsquo; had been specified.
 
   <h3 id=cycle><span class=secno>9.2. </span> Cycling Values: &lsquo;<code
@@ -1428,7 +1434,7 @@
 
   <pre>cycle( &lt;value&gt;# )</pre>
 
-  <p>where <code>&lt;value&lt;</code> is a CSS value that is valid where the
+  <p>where <code>&lt;value&gt;</code> is a CSS value that is valid where the
    expression is placed. If any of the values inside are not valid, then the
    entire &lsquo;<code class=css>cycle()</code>&rsquo; expression is invalid.
    
@@ -1438,7 +1444,7 @@
    value on the parent, or, for the root, the initial value) to the computed
    values <var>C<sub>n</sub></var> returned by the <var>n</var>-th argument
    to &lsquo;<code class=css>cycle()</code>&rsquo;. For the earliest
-   <var>C<sub>n</sub></var> such that <var>C<sub>n</sub></var> ==
+   <var>C<sub>n</sub></var> such that <var>C<sub>n</sub></var> =
    <var>I</var>, the value returned by cycle is <var>C<sub>n+1</sub></var>.
    However, if this <var>C<sub>n</sub></var> is the last value, or if there
    are no <var>C<sub>n</sub></var> that equal <var>I</var>, the computed
@@ -1740,14 +1746,15 @@
    transformed into the <a href="#used-value"><em>used value</em></a> in the
    formatting process. Finally, the computed value is transformed to the <a
    href="#actual-value"><em>actual value</em></a> based on constraints in the
-   user agent.
+   device and user agent.
 
   <h3 id=finding-the-specified-value><span class=secno>10.1. </span>Finding
    the <dfn id=specified-value>specified value</dfn></h3>
 
   <p>The <a href="#specified-value"><em>specified value</em></a> is the
-   output of the cascading and inheritance process <a href="#CSS3CASCADE"
-   rel=biblioentry>[CSS3CASCADE]<!--{{!CSS3CASCADE}}--></a>.
+   output of the <a href="http://www.w3.org/TR/CSS21/cascade.html">cascading
+   and inheritance process</a>. <a href="#CSS21"
+   rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a>
 
   <h3 id=finding-the-computed-value><span class=secno>10.2. </span>Finding
    the <dfn id=computed-value>computed value</dfn></h3>
@@ -1763,13 +1770,11 @@
   <p>For relative values, on the other hand, computation is necessary to find
    the computed values: percentages must be multiplied by a reference value
    (each property defines which value that is), values with relative units
-   (em, ex, px) must be made absolute by multiplying with the appropriate
-   font or pixel size, &lsquo;<code class=property>auto</code>&rsquo; values
-   must be computed by the formulas given with each property, certain
-   keywords (e.g., &lsquo;<code class=property>smaller</code>&rsquo;,
-   &lsquo;<code class=property>bolder</code>&rsquo;) must be replaced
-   according to their definitions. See example (f), (g) and (h) in the table
-   below.
+   (em, ex, vh, vw) must be made absolute by multiplying with the appropriate
+   reference size, certain keywords (e.g., &lsquo;<code
+   class=property>smaller</code>&rsquo;, &lsquo;<code
+   class=property>bolder</code>&rsquo;) must be replaced according to their
+   definitions. See example (f), (g) and (h) in the table below.
 
   <p>Also, relative URIs are computed into absolute URIs at this stage. The
    computed value of invalid and absolute URIs is the same as the specified

Index: Overview.src.html
===================================================================
RCS file: /sources/public/csswg/css3-values/Overview.src.html,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -d -r1.89 -r1.90
--- Overview.src.html	15 Aug 2011 23:09:05 -0000	1.89
+++ Overview.src.html	16 Aug 2011 18:37:15 -0000	1.90
@@ -286,25 +286,25 @@
 		<pre>table { border-collapse: separate }</pre>
 	</div>
 
-<h4 id="initial-inherit">
-The ''initial'' and ''inherit'' keywords</h4>
+<h4 id="common-keywords">
+CSS-wide keywords: ''initial'' and ''inherit''</h4>
 
 	<p>As defined <a href="#component-types">above</a>,
 	all properties accept the ''initial'' and ''inherit'' keywords,
-	which represent value concepts common to all CSS properties.
+	which represent value computations common to all CSS properties.
 
 	<p>The <dfn>''inherit''</dfn> keyword is
 	<a href="http://www.w3.org/TR/CSS21/cascade.html#value-def-inherit">defined</a>
 	in [[!CSS21]].
 
-	<p>The <dfn>''initial''</dfn> keyword represents the value that
+	<p>The <dfn>''initial''</dfn> keyword represents the specified value that
 	is designated as the property's initial value. [[CSS3CASCADE]]
 
 	<p class="issue">Should these keywords affect the specified or computed
 	value? See <a href="http://lists.w3.org/Archives/Public/www-style/2011Jan/0075.html">various</a>
 	<a href="http://lists.w3.org/Archives/Public/www-style/2011May/0402.html">issues</a>.
 
-<p class="issue">Would it be useful to have a 'default' value, defined
+<p class="issue">Would it be useful to have a value defined
 to be equivalent to <span class="css">'inherit'</span> for properties
 that are inherited by default and equivalent to <span
 class="css">'initial'</span> for properties that are not inherited by
@@ -314,6 +314,13 @@
 inherited by default or not (which isn't obvious for some properties,
 such as text-decoration and visibility).</p>
 
+<p class="issue">It's been requested to have a value that rolls back
+to the bottom of that level of the cascade, e.g. for an author rule
+it would roll back to the end of the user cascade, for a user rule
+it would roll back to the end of the UA cascade, and for the UA it
+would roll back to ''initial''/''inherit''. Is that something we should
+add?
+
 <h3 id="identifiers">
 User-defined Identifiers: the ''&lt;identifier&gt;'' type</h3>
 

Received on Tuesday, 16 August 2011 18:37:19 UTC