|
41 | 41 |
|
42 | 42 | <header> |
43 | 43 | <h1>Implementation Report for the CSS Writing Modes Level 3</h1> |
44 | | - <time datetime="2019-09-19">19 September 2019</time> |
| 44 | + <time datetime="2019-10-01">01 October 2019</time> |
45 | 45 | </header> |
46 | 46 |
|
47 | 47 | <nav> |
@@ -84,9 +84,39 @@ <h3 id=summary><a href="#summary" class=self-link></a>1.1. Summary</h3> |
84 | 84 | 9 of the tests that do pass in two implementations |
85 | 85 | do so by <a href="#careful">taking into account non browser implementations</a>. |
86 | 86 |
|
87 | | -<!-- |
88 | | -<p><strong>The Candidate Recommendation exit criteria are therefore not fulfilled.</strong> |
89 | | ---> |
| 87 | +The CSS-WG has examined the <a href="#pb">remaining failing tests</a>, |
| 88 | +and based on the following considerations, |
| 89 | +believes that |
| 90 | +<strong>the Candidate Recommendation exit criteria are fulfilled</strong>: |
| 91 | + |
| 92 | +<ul> |
| 93 | + <li> |
| 94 | + The success criteria established in the working group charter speficy that |
| 95 | + <q>In order to advance to Proposed Recommendation, |
| 96 | + each module is expected to have at least two independent implementations |
| 97 | + of each of feature defined in the specification</q>. |
| 98 | + With multiple browser engines (as well as non browsers) implementing the specification, |
| 99 | + this criterion is fulfilled, |
| 100 | + even though there remains a few tests for certain specificities of some features |
| 101 | + that do not yet have two passing implementations. |
| 102 | + |
| 103 | + <li> |
| 104 | + Quite a few of the failing tests have work-in-progress implementations. |
| 105 | + |
| 106 | + <li> |
| 107 | + CSS Writing Modes Level 3 is a particularly complex specification, |
| 108 | + affecting all aspects of layout. |
| 109 | + For a project of that complexity, |
| 110 | + no matter how much time we spend on it, |
| 111 | + there will always be a few more bugs to fix, |
| 112 | + and a few more nuances to get right. |
| 113 | + We should not let the fact that we're being thorough with testing |
| 114 | + impede the progress of specification, |
| 115 | + and we believe that it is appropriate to signal to the broader community |
| 116 | + the degree of stability of this specification |
| 117 | + by publishing it as a Proposed Recommendation, |
| 118 | + then as a W3C Recommendation. |
| 119 | +</ul> |
90 | 120 |
|
91 | 121 | <p>9 of 27 optional tests pass in two or more browser implementations; |
92 | 122 | 18 do not. |
@@ -302,7 +332,7 @@ <h2 id=method><a href="#method" class=self-link></a>2. Methodology</h2> |
302 | 332 | or to the archived public discussion mailing list for CSS test suites, <a href="mailto:public-css-testsuite@w3.org">public-css-testsuite@w3.org</a>. |
303 | 333 |
|
304 | 334 | <p>A <a href="https://test.csswg.org/harness/results/css-writing-modes-3_dev/">continuously updated version of the test suite</a> is available. |
305 | | -This report was prepared using the tests and their results as of 16 September 2019. |
| 335 | +This report was prepared using the tests as of 16 September 2019. |
306 | 336 |
|
307 | 337 | <p class=note>Note: Many of the tests in this test suite are somewhat old, |
308 | 338 | and interact poorly with the automation mechanism of the web-platform-test project. |
|
0 commit comments