44
55< title > Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</ title >
66< link rel ="stylesheet " href ="style/default.css " type ="text/css ">
7- < link rel ="stylesheet " href ="http://www.w3.org/StyleSheets/TR/W3C-ED .css " type ="text/css ">
7+ < link rel ="stylesheet " href ="http://www.w3.org/StyleSheets/TR/W3C-PR .css " type ="text/css ">
88< link rel ="next " href ="about.html ">
99< link rel ="contents " href ="cover.html#minitoc ">
1010< link rel ="CSS-properties " href ="propidx.html " title ="properties ">
2525 src ="http://www.w3.org/Icons/w3c_home " width ="72 "> </ a >
2626
2727 < h1 id ="title "> Cascading Style Sheets Level 2 Revision 1 (CSS 2.1) Specification</ h1 >
28- < h2 id ="W3C-doctype "> W3C Editors Draft DD MMMMM YYYY </ h2 >
28+ < h2 id ="W3C-doctype "> W3C Proposed Recommendation 12 April 2011 </ h2 >
2929
3030 < dl >
3131 < dt > This version:
32- < dd > < a href ="http://www.w3.org/TR/YYYY/ED -CSS2-YYYYMMDD ">
33- http://www.w3.org/TR/YYYY/ED -CSS2-YYYYMMDD </ a >
32+ < dd > < a href ="http://www.w3.org/TR/2011/PR -CSS2-20110412 ">
33+ http://www.w3.org/TR/2011/PR -CSS2-20110412 </ a >
3434 < dt > Latest version:
3535 < dd > < a href ="http://www.w3.org/TR/CSS2 ">
3636 http://www.w3.org/TR/CSS2</ a >
@@ -55,7 +55,7 @@ <h2 id="W3C-doctype">W3C Editors Draft DD MMMMM YYYY</h2>
5555 </ dl >
5656
5757 < p > Please refer to the < a
58- href ="http://www.w3.org/Style/css2-updates/ED -CSS2-YYYYMMDD -errata.html "> < strong >
58+ href ="http://www.w3.org/Style/css2-updates/PR -CSS2-20110412 -errata.html "> < strong >
5959 errata</ strong > </ a > for this document.
6060
6161 < p > This document is also available in these non-normative formats:
@@ -125,25 +125,17 @@ <h2 id=abstract>Abstract</h2>
125125
126126< h2 id =status > Status of this document</ h2 >
127127
128- < p > This is the editor's draft of the next version of this
129- specification.
130- It
131- is < em > not a W3C Technical Report.</ em > The CSS working group has
132- decided to make it available, but has not fully
133- reviewed it. It is very likely to contain editing errors.
134-
135- <!--
136128< p > < em > This section describes the status of this document at the time
137129of its publication. Other documents may supersede this document. A
138130list of current W3C publications and the latest revision of this
139131technical report can be found in the < a
140132href ="http://www.w3.org/TR/ "> W3C technical reports index at
141133http://www.w3.org/TR/.</ a > </ em > </ p >
142134
143- <p>Publication as a Working Draft does not imply endorsement by the
144- W3C Membership. This is a draft document and may be updated, replaced
145- or obsoleted by other documents at any time. It is inappropriate to
146- cite this document as other than work in progress.</p>
135+ < p > Publication as a Proposed Recommendation does not imply endorsement
136+ by the W3C Membership. This is a draft document and may be updated,
137+ replaced or obsoleted by other documents at any time. It is
138+ inappropriate to cite this document as other than work in progress.
147139
148140< p > The (< a
149141href ="http://lists.w3.org/Archives/Public/www-style/ "> archived</ a > )
@@ -174,109 +166,10 @@ <h2 id=status>Status of this document</h2>
174166href ="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure "> section 6 of
175167the W3C Patent Policy</ a > .</ p >
176168
177- <p>A <a href="/Style/CSS/Test/">test suite</a> and
178- an implementation report will be provided before the document becomes
179- a Proposed Recommendation.</p>
180- -->
181-
182- < h3 class ="no-num " id ="crec "> Candidate Recommendation Exit Criteria</ h3 >
183-
184- < p > For this specification to be proposed as a W3C Recommendation, the
185- following conditions shall be met. There must be at least two
186- independent, interoperable implementations of each feature. Each
187- feature may be implemented by a different set of products, there is no
188- requirement that all features be implemented by a single product. For
189- the purposes of this criterion, we define the following terms:
190- < dl >
191- < dt > independent < dd > each implementation must be developed by a
192- different party and cannot share, reuse, or derive from code used by
193- another qualifying implementation. Sections of code that have no
194- bearing on the implementation of this specification are exempt from
195- this requirement.
196-
197- < dt > interoperable < dd > passing the respective test case(s) in the
198- official CSS test suite, or, if the implementation is not a Web
199- browser, an equivalent test. Every relevant test in the test suite
200- should have an equivalent test created if such a user agent (UA) is to
201- be used to claim interoperability. In addition if such a UA is to be
202- used to claim interoperability, then there must one or more additional
203- UAs which can also pass those equivalent tests in the same way for the
204- purpose of interoperability. The equivalent tests must be made
205- publicly available for the purposes of peer review.
206-
207- < dt > implementation < dd > a user agent which:
208- < ol class =inline >
209- < li > implements the specification.
210-
211- < li > is available to the general public. The implementation may be a
212- shipping product or other publicly available version (i.e., beta
213- version, preview release, or “nightly build”). <!--
214- Non-shipping product releases must have implemented the feature(s) for
215- a period of at least one month in order to demonstrate stability. -->
216-
217- < li > is not experimental (i.e., a version specifically designed to pass
218- the test suite and is not intended for normal usage going forward).
219- </ ol >
220- </ dl >
221-
222- < p > A minimum of six months of the CR period must have elapsed. This is
223- to ensure that enough time is given for any remaining major errors to
224- be caught.
225-
226- < p > Features will be dropped if two or more interoperable
227- implementations are not found by the end of the CR period.
228-
229- < p > Features may/will also be dropped if adequate/sufficient (by
230- judgment of CSS WG) tests have not been produced for those feature(s)
231- by the end of the CR period.
232-
233-
234- < h3 id =at-risk > Features at risk</ h3 >
235-
236- < p > The working group has identified the following features as being
237- currently poorly implemented by UAs. They are therefore most at risk
238- of being removed from CSS 2.1 when exiting CR. (Any changes of this
239- nature will still result in the specification being returned to last
240- call.) Implementors are urged to implement these features, or correct
241- bugs in their implementations, if they wish to see these features remain
242- in this specification.</ p >
243- < dl >
244- < dt > New 'list-style-type' values</ dt >
245- < dd >
246- < ul >
247- < li > 'armenian'</ li >
248- < li > 'georgian'</ li >
249- < li > 'lower-greek'</ li >
250- </ ul >
251- < p > Implementors are advised to look at CSS3 Lists instead, where these and
252- many other new values not found in CSS1 are defined in detail.
253- < a href ="refs.html#ref-CSS3LIST " rel ="biblioentry " class ="noxref "> < span class ="informref "> [CSS3LIST]</ span > </ a > </ p >
254- < dt > Support for multiple ID attributes for the ID selector
255- < dd >
256- < p > Because implementations are not expected to support multiple IDs
257- per element soon, this feature may be made informative. The W3C
258- Selectors specification will continue to have this feature
259- normatively. (< a href ="selector.html#id-selectors "> Section
260- 5.9.</ a > )
261- </ dd >
262- < dt > Automatic table layout algorithm
263- < dd >
264- < p > The input to the suggested (non-normative) automatic layout
265- algorithm for tables is restricted to (1) the containing block width
266- and (2) the content and properties of the table and its
267- children. This restriction may be lifted.
268- < dt > Quotes
269- < dd >
270- < p > The < span class ="propinst-quotes "> 'quotes'</ span > property and the
271- 'open-quote', 'close-quote', 'no-open-quote' and 'no-close-quote'
272- keywords may be dropped.
273- < dt > BODY element in XHTML
274- < dd >
275- < p > The effect of < a href ="visufx.html#overflow "> 'overflow'</ a > and < a
276- href ="colors.html#background "> 'background'</ a > is different on BODY elements
277- in HTML than on other elements. It may be that the exceptional
278- handling of BODY in HTML is extended to BODY in XHTML1.
279- </ dl >
169+ < p > The Working Group has created a < a href ="/Style/CSS/Test/ "> test
170+ suite</ a > and
171+ an < a href ="/Style/CSS/Test/CSS2.1/20110323/reports/ "> implementation
172+ report.</ a >
280173
281174<!--NewPage--> <!-- this is for html2ps -->
282175< div class ="toc ">
0 commit comments