[css2] Status section for CR and final issues (Håkon's, but edited by Kimberly).

bert-github · bert-github · commit 300e3e65cd66 · 2004-02-14T00:59:12.000Z
--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402208
diff --git a/css2/cascade.src b/css2/cascade.src
@@ -1,9 +1,10 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: cascade.src,v 2.46 2003-10-17 17:52:46 bbos Exp $ -->
+<!-- $Id: cascade.src,v 2.47 2004-02-14 00:59:12 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Assigning property values, Cascading, and Inheritance</TITLE>
+<!-- Changed by Kimberly Blessing, 2004-02-13 -->
 </HEAD>
 <BODY>
 
@@ -22,11 +23,11 @@ calculation: the value is determined through specification (the
 (the "computed value"), and finally transformed according to
 the limitations of the local environment (the "actual value").
 
-<h3>
-<span class="index-def" title="specified value">
+
+<h3><span class="index-def" title="specified value">
 <a name="specified-value">Specified values</a></span></h3>
 
-<p>User agents must first assign a specified value to a property based
+<p>User agents must first assign a specified value to each property based
 on the following mechanisms (in order of precedence):</p>
 
 <ol>
@@ -35,22 +36,17 @@ on the following mechanisms (in order of precedence):</p>
 <li>Otherwise use the property's <span class="index-def" title="initial value">initial value</span>. The initial value of each property is indicated in the property's definition. 
 </ol>
 
-<p>Since it has no parent, the root of the <a
-href="conform.html#doctree">document tree</a> cannot use values from
-the parent element; in this case, the initial value is used if
-necessary.
-
 
 <h3><span class="index-def" title="computed value">
-<a name="computed-value">Computed values</a>
-</span>
-</h3>
+<a name="computed-value">Computed values</a></span></h3>
+
+<p>Specified values are resolved to computed values during the cascade;
+for example valid relative URIs are made absolute and 'em' and 'ex'
+units are computed to pixel or absolute lengths. Computing a value
+never requires the user agent to render the document.
 
-<p>Specified values may be absolute (i.e., they are not specified
-relative to another value, as in 'red' or '2mm') or relative (i.e.,
-they are specified relative to another value, as in 'auto', '2em', and
-'12%'). For absolute values, no computation is needed to find the
-computed value.
+<p>The computed value of invalid and absolute URIs is the specified
+value.
 
 <p>Relative values, on the other hand, must be transformed into
 computed values: percentages must be multiplied by a reference value
@@ -74,15 +70,27 @@ properties may define the computed value of a property for an element
 to depend on whether the property applies to that element.
 
 
+<h3><span class="index-def" title="used value">
+<a name="used-value">Used values</a></span></h3>
+
+<p>Computed values can be relative to each other; for example a width
+could be set as a percentage, which is dependent on the containing
+block's width. The <dfn id="usedValue">used value</dfn> is the
+result of taking the computed value and resolving these dependencies
+into a final absolute value used for the actual layout.
+
+
 <h3><span class="index-def" title="actual value">
 <a name="actual-value">Actual values</a></span></h3>
 
-<p>A computed value is in principle ready to be used, but a user agent
-may not be able to make use of the value in a given environment. For
-example, a user agent may only be able to render borders with integer
-pixel widths and may therefore have to approximate the computed
-width. The actual value is the computed value after any approximations
-have been applied.
+<p>A used value is in principle the value used for rendering, but a
+user agent may not be able to make use of the value in a given
+environment. For example, a user agent may only be able to render
+borders with integer pixel widths and may therefore have to
+approximate the computed width, or the user agent may be forced to
+use only black and white shades instead of full colour. The actual
+value is the used value after any approximations have been applied.
+
 
 <h2><a name="inheritance">Inheritance</a></h2>
 
@@ -114,7 +122,7 @@ For example, given the following style sheet:</P>
 
 <pre>
 body { font-size: 10pt }
-h1 { font-size: 120% }
+h1 { font-size: 130% }
 </pre>
 
 <p>and this document fragment:
@@ -126,13 +134,13 @@ h1 { font-size: 120% }
 </pre>
 
 <p>the <span class="prop-inst-font-size">'font-size'</span> property
-for the H1 element will have the computed value '12pt' (120% times
+for the H1 element will have the computed value '13pt' (130% times
 10pt, the parent's value). Since the computed value of <span
 class="propinst-font-size">'font-size'</span> is inherited, the EM
-element will have the computed value '12pt' as well.  If the
-user agent does not have the 12pt font available, the
+element will have the computed value '13pt' as well.  If the
+user agent does not have the 13pt font available, the
 actual value of <span class="propinst-font-size">'font-size'</span>
-for both H1 and EM might be, for example, '11pt'.
+for both H1 and EM might be, for example, '12pt'.
 </div>
 
 <h3>The <span class="index-def" title="inherit, definition
@@ -239,10 +247,16 @@ browsers, the EM element in HTML is presented using an italic
 font). See <a href="sample.html">A sample style sheet for HTML
 </a> for a recommended default style sheet for HTML documents.
 
-<P>Note that the default style sheet may change if system settings are
-modified by the user (e.g., system colors). However, due to
-limitations in a user agent's internal implementation, it may be
-impossible to change the values in the default style sheet.
+<p class="note">Note that the user may modify system settings (e.g. 
+system colors) that affect the default style sheet. However, some user 
+agent implementations make it impossible to change the values in the 
+default style sheet.
+
+
+Note that the user may modify system settings
+(e.g. system colors) that affect the default style sheet. However,
+some user agent implementations make it impossible to change the
+values in the default style sheet.
 </ul>
 
 <P>Style sheets from these three origins will overlap in scope, and
@@ -257,10 +271,6 @@ rules in user style sheets. Precedence is reversed, however, for
 "!important" rules. All user and author rules have more weight
 than rules in the UA's default style sheet.
 
-<P>Rules specified in a given style sheet override rules of the same
-weight imported from other style sheets. Imported style sheets can
-themselves import and override other style sheets, recursively, and
-the same precedence rules apply.
 
 <H3><a name="cascading-order">Cascading order</a></H3>
 
@@ -274,7 +284,7 @@ must apply the following sorting order:</p>
       Declarations apply if the associated selector <A
       HREF="selector.html">matches</A> the element in question.
 
-    <LI>Sort by weight (normal or important) and origin (author, user, or user agent). In ascending order:
+    <LI>Sort by importance (normal or important) and origin (author, user, or user agent). In ascending order:
 
 <ol>
 <li>user agent style sheets
@@ -311,23 +321,20 @@ and user style sheets. By default, rules in an author's style
 sheet override those in a user's style sheet (see cascade
 rule 3). 
 
-<P>However, for balance, an "!important" declaration (the keywords "!"
-and "important" follow the declaration) takes precedence over a normal
-declaration.  Both author and user style sheets may contain
+<P>However, for balance, an "!important" declaration (the delimiter token 
+"!" and keyword "important" follow the declaration) takes precedence over 
+a normal declaration.  Both author and user style sheets may contain
 "!important" declarations, and user "!important" rules override author
 "!important" rules. This CSS feature improves accessibility
 of documents by giving users with special requirements (large
 fonts, color combinations, etc.) control over presentation.
 
-
-
 <P>Declaring a <span class="index-inst" title="shorthand
 property">shorthand property</span> (e.g., <span
 class="propinst-background">'background'</span>) to be "!important" is
 equivalent to declaring all of its sub-properties to be "!important".
 
 <div class="example"> 
-
 <P>The first rule in the user's style sheet in the following example
 contains an "!important" declaration, which overrides the corresponding
 declaration in the author's style sheet.  The second declaration
@@ -347,7 +354,7 @@ p { font-size: 18pt }
 
 /* From the author's style sheet */
 p { text-indent: 1.5em !important }
-p { font: 12pt sans-serif !important }
+p { font: normal 12pt sans-serif !important }
 p { font-size: 24pt }
 </PRE>
 </div>
@@ -418,7 +425,7 @@ defined as an "ID" in the source document's DTD.
 
 <H3>Precedence of non-CSS presentational hints</H3> 
 
-<P>The UA may choose to honor presentational attributes in the source
+<P>The UA may choose to honor presentational attributes an HTML source
 document. If so, these attributes are translated to the corresponding
 CSS rules with specificity equal to 0, and are treated as if they were
 inserted at the start of the author style sheet. They may therefore be
@@ -437,13 +444,11 @@ onclick, ondblclick, onfocus, onkeydown, onkeypress, onkeyup, onload,
 onload, onmousedown, onmousemove, onmouseout, onmouseover, onmouseup,
 onreset, onselect, onsubmit, onunload, onunload, profile, prompt,
 readonly, rel, rev, rowspan, scheme, scope, selected, shape, span,
-src, standby, start, style, summary, title, type, usemap, value,
-valuetype, version.
+src, standby, start, style, summary, title, type (except on LI, OL and 
+UL elements), usemap, value, valuetype, version.
 
-<P>For XHTML and other languages written in XML, no attribute should
-be considered presentational. The styling of elements and
-non-presentational attributes should be handled in the user agent
-stylesheet.
+<P>For other languages, all document language-based styling should be 
+handled in the user agent style sheet.
 
 <div class="example">
 
diff --git a/css2/conform.src b/css2/conform.src
@@ -1,9 +1,10 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: conform.src,v 2.56 2003-06-09 15:44:07 bbos Exp $ -->
+<!-- $Id: conform.src,v 2.57 2004-02-14 00:59:12 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Conformance: requirements and recommendations</TITLE>
+<!-- Changed by Kimberly Blessing, 2004-02-13 -->
 </HEAD>
 <BODY>
 <H1>Conformance: Requirements and Recommendations</H1>
@@ -130,7 +131,7 @@ sub-elements.
 
 <dt><strong><span class="index-def" title="ignore">Ignore</span></strong>
 
-<dd>This term has three slightly different meanings this specification. First, a CSS parser must follow certain rules when it discovers unknown or illegal syntax in a style sheet. The parser must then ignore certain parts of the style sheets. The exact rules for what parts must be ignored is given in these section: <a href="syndata.html#q8">Declarations and properties</a>, <a href="syndata.html#parsing-errors">Rules for handling parsing errors</a>, <a href="syndata.html#q20">Unsupported Values</a>, or may be explained in the text where the term "ignore" appears. Second, a user agent may (and, in some cases must) disregard certain properties or values in the style sheet even if the syntax is legal. For example, table-column-group elements cannot have borders around them, so the border properties must be ignored.
+<dd>This term has two slightly different meanings this specification. First, a CSS parser must follow certain rules when it discovers unknown or illegal syntax in a style sheet. The parser must then ignore certain parts of the style sheets. The exact rules for what parts must be ignored is given in these section: <a href="syndata.html#q8">Declarations and properties</a>, <a href="syndata.html#parsing-errors">Rules for handling parsing errors</a>, <a href="syndata.html#q20">Unsupported Values</a>, or may be explained in the text where the term "ignore" appears. Second, a user agent may (and, in some cases must) disregard certain properties or values in the style sheet even if the syntax is legal. For example, table-column-group elements cannot have borders around them, so the border properties must be ignored.
 
 
 <dt><strong><span class="index-def" title="rendered
diff --git a/css2/cover.src b/css2/cover.src
@@ -56,7 +56,7 @@
 
   <p class="copyright"><a
   href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">
-  Copyright</a> &copy; 2003 <a href="http://www.w3.org/"><abbr
+  Copyright</a> &copy; 2004 <a href="http://www.w3.org/"><abbr
   title="World Wide Web Consortium">W3C</abbr></a><sup>&reg;</sup> (<a
   href="http://www.lcs.mit.edu/"><abbr title="Massachusetts Institute
   of Technology">MIT</abbr></a>, <a
@@ -104,36 +104,34 @@ that are implemented interoperably at the date of publication of the Recommendat
 
 <h2 id=status>Status of this document</h2>
 
-<p>This is a W3C <a
-href="http://www.w3.org/Consortium/Process/Process-19991111/tr.html#last-call">Last
-Call Working Draft</a>. "Last call" means that the working group
-believes that this specification is ready and therefore wishes this to
-be the last call for comments. If the feedback is positive, the
-working group plans to submit it for consideration as a <a
-href="http://www.w3.org/TR/#About">W3C Candidate Recommendation</a>.
-Comments can be sent until <strong>10 October 2003.</strong>
+<p><em>This section describes the status of this document at the time
+of its publication. Other documents may supersede it. A list of
+current W3C publications and the latest revision of this technical
+report can be found in the <a href="http://www.w3.org/TR/">W3C
+technical reports index at http://www.w3.org/TR/</a>.</em>
 
-<p>This document is produced by the <a
-href="http://www.w3.org/Style/Group/">CSS working group</a> (part of
-the <a href="http://www.w3.org/Style/">Style Activity</a>, see <a
-href="http://www.w3.org/Style/Activity">summary</a>).
+<p>This is a W3C Candidate Recommendation, which means the
+specification has been widely reviewed and W3C recommends that it be
+implemented. It will remain Candidate Recommendation <a
+href="#crec">at least until September 2004.</a>
+
+<p>Publication as a Candidate Recommendation does not imply
+endorsement by the W3C Membership. It is inappropriate to cite this
+document as other than work in progress.
 
 <p>The (<a
 href="http://lists.w3.org/Archives/Public/www-style/">archived</a>)
 public mailing list <a
 href="mailto:www-style@w3.org">www-style@w3.org</a> (see <a
 href="http://www.w3.org/Mail/Request">instructions</a>) is preferred
-for discussion of this and other drafts in the Style area. When
-commenting on this draft, please put the text "CSS21" in the subject,
-preferably like this: "[CSS21] &lt;summary of comment&gt;"
+for discussion of this and other specifications in the Style area.
+When commenting on this document, please put the text "CSS21" in the
+subject, preferably like this: "[CSS21] &lt;summary of comment&gt;"
 
-<p><em>This section describes the status of this document at the time
-of its publication. Other documents may supersede this document. A
-list of current W3C publications and the latest revision of this
-technical report can be found in the <a href="/TR/">W3C technical
-reports index</a> at <a href="/TR/">http://www.w3.org/TR/.</a> It is
-inappropriate to use W3C Working Drafts as reference material or to
-cite them as other than "work in progress."</em>
+<p>This document is produced by the <a
+href="http://www.w3.org/Style/members">CSS working group</a> (part of
+the <a href="http://www.w3.org/Style/">Style Activity</a>, see <a
+href="http://www.w3.org/Style/Activity">summary</a>).
 
 <p>Patent disclosures relevant to CSS may be found on the Working
 Group's public <a
diff --git a/css2/generate.src b/css2/generate.src
@@ -3,6 +3,7 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Generated content, automatic numbering, and lists</title>
+<!-- Changed by Kimberly Blessing, 2004-02-13 -->
 </head>
 <body>
 <h1 align="center">
@@ -239,6 +240,7 @@ more information on the "\A" escape sequence.
 h1:before {
     display: block;
     text-align: center;
+	white-space: pre;
     content: "chapter\A hoofdstuk\A chapitre"
 }
 </pre>
diff --git a/css2/media.src b/css2/media.src
@@ -1,10 +1,10 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: media.src,v 2.31 2003-11-06 23:34:42 bbos Exp $ -->
+<!-- $Id: media.src,v 2.32 2004-02-14 00:59:12 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Media types</TITLE>
-<!-- Changed by: Tantek Celik and H&aring;kon Lie, 2002-11-16 -->
+<!-- Changed by Kimberly Blessing, 2004-02-13 -->
 </HEAD>
 <BODY>
 <H1>Media types</H1>
@@ -114,8 +114,8 @@ properties that apply to that media type.
 <P>The names chosen for CSS media types reflect target devices for
 which the relevant properties make sense. In the following list of CSS
 media types the names of media types are normative, but the
-parenthetical descriptions are informative. Likewise, the "Media"
-field in the description of each property is informative.
+descriptions are informative. Likewise, the "Media" field in the 
+description of each property is informative.
 
 <dl>
 <dt><strong>all</strong>
@@ -175,15 +175,14 @@ can only support one media type when rendering a document. However,
 user agents may have different modes which support different media
 types.
 
+<P>Unknown media type names should not result in the @media rule being ignored.
 
 <!--
 <P>Due to rapidly changing technologies, CSS2 does not specify a
 definitive list of media types that may be values for <span
 class="index-inst" title="@media">@media</span>.
 -->
 
-
-
 <div class="note"><P>
 <em><strong>Note.</strong>
 Future versions of CSS may extend the list of media types. Authors
@@ -260,7 +259,7 @@ between media groups and media types:</P>
 <TR><TH>aural<TD align="center">continuous<TD align="center">speech, audio<TD align="center">N/A<TD align="center">both</TR>
 -->
 <TR><TH>braille<TD align="center">continuous<TD align="center">tactile<TD align="center">grid<TD align="center">both</TR>
-<TR><TH>emboss<TD align="center">paged<TD align="center">tactile<TD align="center">grid<TD align="center">static</TR>
+<TR><TH>embossed<TD align="center">paged<TD align="center">tactile<TD align="center">grid<TD align="center">static</TR>
 <TR><TH>handheld<TD align="center">both<TD align="center">visual, audio, speech<TD
 align="center">both<TD align="center">both</TR>
 <TR><TH>print<TD align="center">paged<TD align="center">visual<TD
diff --git a/css2/page.src b/css2/page.src
@@ -1,9 +1,10 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <html lang="en">
-<!-- $Id: page.src,v 2.40 2003-11-06 23:34:42 bbos Exp $ -->
+<!-- $Id: page.src,v 2.41 2004-02-14 00:59:12 bbos Exp $ -->
 <HEAD>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <TITLE>Paged media</TITLE>
+<!-- Changed by Kimberly Blessing, 2004-02-13 -->
 </HEAD> 
 
 <body>
@@ -308,7 +309,7 @@ section on <a href="visuren.html#line-box">line boxes</a>.
 <ol>
 <li>
 In the vertical margin between block boxes. When a page
-break occurs here, the <a href="cascade.html#computed-value">computed
+break occurs here, the <a href="cascade.html#used-value">used
 values</a> of the relevant
 <span class="propinst-margin-top">'margin-top'</span>
 and <span class="propinst-margin-bottom">'margin-bottom'</span>
diff --git a/css2/sample.src b/css2/sample.src
