@@ -140,8 +140,6 @@ Group's public <a
140140href="http://www.w3.org/Style/CSS/Disclosures">patent disclosure
141141page.</a></p>
142142
143- <ins cite="http://www.damowmow.com/temp/csswg/css21/issues"
144- title="issue 15">
145143<h3 class="no-num" id="crec">Candidate Recommendation Exit Criteria</h3>
146144
147145<p>For this specification to exit the CR stage, the following
@@ -191,73 +189,15 @@ conditions must be met:</p>
191189 errors to be caught.</p></li>
192190 <li><p>The CR period will be extended if implementations are slow to
193191 appear.</p></li>
194- <li><p>Features will be dropped (thus reducing the list of "all"
192+ <li><p>Features that were not in CSS1 will be dropped (thus reducing
193+ the list of "all"
195194 features mentioned above) if two or more interoperable
196195 implementations of those features are not found by the end of the CR
197196 period.</p></li>
198197 <li><p>Features will also be dropped if sufficient and adequate
199198 tests (by judgment of the working group) have not been produced for
200199 those features by the end of the CR period.</p></li>
201200 </ol>
202- </ins>
203-
204- <del cite="http://www.damowmow.com/temp/csswg/css21/issues"
205- title="issue 15">
206- <p>For this specification to exit the CR stage, the following
207- conditions shall be met:
208- <ol>
209- <li><p>There must be at least two interoperable implementations
210- implementing 'all' the features. An implementation can implement a
211- superset of the features and claim conformance to the profile. For
212- the purposes of this criterion, we define the following terms:
213-
214- <dl>
215- <dt>feature
216- <dd>
217- <p>An individual test case in the test suite.
218-
219- <dt>interoperable
220- <dd>
221- <p>passing the respective test case(s) in the CSS test suite, or,
222- if the implementation is not a web browser, an equivalent test.
223- Every relevant test in the test suite should have an equivalent
224- test created if such a UA is to be used to claim interoperability.
225- In addition if such a UA is to be used to claim interoperability,
226- then there must one or more additional UAs which can also pass
227- those equivalent tests in the same way for the purpose of
228- interoperability. The equivalent tests must be made publicly
229- available for the purposes of peer review.
230-
231- <dt>implementation
232- <dd>
233- <p>a user agent which:
234- <ol>
235- <li>implements the feature.
236-
237- <li>is available (i.e. publicly downloadable or available
238- through some other public point of sale mechanism). This is the
239- "show me" requirement.
240-
241- <li>is shipping (i.e. development, private or unofficial
242- versions are insufficient).
243-
244- <li>is not experimental (i.e. is intended for a wide audience
245- and could be used on a daily basis.)
246- </ol>
247- </dl>
248-
249- <li><p>A minimum of sixth months of the CR period must have elapsed.
250- This is to ensure that enough time is given for any remaining major
251- errors to be caught.
252-
253- <li><p>Features may/will be dropped if two or more interoperable
254- implementations are not found by the end of the CR period.
255-
256- <li><p>Features may/will also be dropped if adequate/sufficient (by
257- judgment of CSS WG) tests have not been produced for those
258- feature(s) by the end of the CR period.
259- </ol>
260- </del>
261201
262202<!--NewPage--><!-- this is for html2ps -->
263203<div class="toc">
0 commit comments