[css2] Updated status section for PR.

--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%403203

Author: bert-github

css2/cover.src

@@ -110,25 +110,17 @@ CSS3 Module that includes those feature(s)).
 
 <h2 id=status>Status of this document</h2>
 
-<p>This is the editor's draft of the next version of this
-specification.
-It
-is <em>not a W3C Technical Report.</em> The CSS working group has
-decided to make it available, but has not fully
-reviewed it. It is very likely to contain editing errors.
-
-<!--
 <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="http://www.w3.org/TR/">W3C technical reports index at
 http://www.w3.org/TR/.</a></em></p>
 
-<p>Publication as a Working Draft does not imply endorsement by the
-W3C Membership. This is a draft document and may be updated, replaced
-or obsoleted by other documents at any time. It is inappropriate to
-cite this document as other than work in progress.</p>
+<p>Publication as a Proposed Recommendation does not imply endorsement
+by the W3C Membership. This is a draft document and may be updated,
+replaced or obsoleted by other documents at any time. 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>)
@@ -159,109 +151,10 @@ with <a
 href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of
 the W3C Patent Policy</a>.</p>
 
-<p>A <a href="/Style/CSS/Test/">test suite</a> and
-an implementation report will be provided before the document becomes
-a Proposed Recommendation.</p>
--->
-
-<h3 class="no-num" id="crec">Candidate Recommendation Exit Criteria</h3>
-
-<p>For this specification to be proposed as a W3C Recommendation, the
-following conditions shall be met. There must be at least two
-independent, interoperable implementations of each feature. Each
-feature may be implemented by a different set of products, there is no
-requirement that all features be implemented by a single product. For
-the purposes of this criterion, we define the following terms:
-<dl>
-<dt>independent <dd>each implementation must be developed by a
-different party and cannot share, reuse, or derive from code used by
-another qualifying implementation. Sections of code that have no
-bearing on the implementation of this specification are exempt from
-this requirement.
-
-<dt>interoperable <dd>passing the respective test case(s) in the
-official CSS test suite, or, if the implementation is not a Web
-browser, an equivalent test. Every relevant test in the test suite
-should have an equivalent test created if such a user agent (UA) is to
-be used to claim interoperability. In addition if such a UA is to be
-used to claim interoperability, then there must one or more additional
-UAs which can also pass those equivalent tests in the same way for the
-purpose of interoperability. The equivalent tests must be made
-publicly available for the purposes of peer review.
-
-<dt>implementation <dd>a user agent which:
-<ol class=inline>
-<li>implements the specification. 
-
-<li>is available to the general public. The implementation may be a
-shipping product or other publicly available version (i.e., beta
-version, preview release, or &ldquo;nightly build&rdquo;). <!--
-Non-shipping product releases must have implemented the feature(s) for
-a period of at least one month in order to demonstrate stability. -->
-
-<li>is not experimental (i.e., a version specifically designed to pass
-the test suite and is not intended for normal usage going forward).
-</ol>
-</dl>
-
-<p>A minimum of six months of the CR period must have elapsed. This is
-to ensure that enough time is given for any remaining major errors to
-be caught.
-
-<p>Features will be dropped if two or more interoperable
-implementations are not found by the end of the CR period.
-
-<p>Features may/will also be dropped if adequate/sufficient (by
-judgment of CSS WG) tests have not been produced for those feature(s)
-by the end of the CR period.
-
-
-<h3 id=at-risk>Features at risk</h3>
-
-<p>The working group has identified the following features as being
-currently poorly implemented by UAs. They are therefore most at risk
-of being removed from CSS&nbsp;2.1 when exiting CR. (Any changes of this
-nature will still result in the specification being returned to last
-call.) Implementors are urged to implement these features, or correct
-bugs in their implementations, if they wish to see these features remain
-in this specification.</p>
-<dl>
- <dt>New 'list-style-type' values</dt>
- <dd>
-  <ul>
-   <li>'armenian'</li>
-   <li>'georgian'</li>
-   <li>'lower-greek'</li>
-  </ul>
-  <p>Implementors are advised to look at CSS3 Lists instead, where these and
-  many other new values not found in CSS1 are defined in detail.
-  [[-CSS3LIST]]</p>
- <dt>Support for multiple ID attributes for the ID selector
- <dd>
-  <p>Because implementations are not expected to support multiple IDs
-  per element soon, this feature may be made informative. The W3C
-  Selectors specification will continue to have this feature
-  normatively. (<a href="selector.html#id-selectors">Section
-  5.9.</a>)
- </dd>
- <dt>Automatic table layout algorithm
- <dd>
-  <p>The input to the suggested (non-normative) automatic layout
-  algorithm for tables is restricted to (1) the containing block width
-  and (2) the content and properties of the table and its
-  children. This restriction may be lifted.
- <dt>Quotes
- <dd>
- <p>The <span class="propinst-quotes">'quotes'</span> property and the
- 'open-quote', 'close-quote', 'no-open-quote' and 'no-close-quote'
- keywords may be dropped.
- <dt>BODY element in XHTML
- <dd>
- <p>The effect of <a href="visufx.html#overflow">'overflow'</a> and <a
- href="colors.html#background">'background'</a> is different on BODY elements
- in HTML than on other elements. It may be that the exceptional
- handling of BODY in HTML is extended to BODY in XHTML1.
-</dl>
+<p>The Working Group has created a <a href="/Style/CSS/Test/">test
+suite</a> and
+an <a href="/Style/CSS/Test/CSS2.1/20110323/reports/">implementation
+report.</a>
 
 <!--NewPage--><!-- this is for html2ps -->
 <div class="toc">