| OLD | NEW |
|---|
| 1 W3C CSS Test Suite Repository | 1 W3C CSS Test Suite Repository |
| 2 ----------------------------- | 2 ----------------------------- |
| 3 | 3 |
| 4 This repository contains top level directories for all of CSS specs for | 4 This repository contains top level directories for all of CSS specs for |
| 5 which we currently have tests. Place tests in the appropriate directory based | 5 which we currently have tests. Place tests in the appropriate directory based |
| 6 on the first rel="help" link in the test. If you are writing tests for a spec | 6 on the first rel="help" link in the test. If you are writing tests for a spec |
| 7 and it doesn't yet have a directory here, feel free to create it. | 7 and it doesn't yet have a directory here, feel free to create it. |
| 8 | 8 |
| 9 There are a few directories that do not map to specifications: | 9 There are a few directories that do not map to specifications: |
| 10 | 10 |
| (...skipping 22 matching lines...) Expand all Loading... |
| 33 For CSS tests, you must also be sure you’re linking to a specific level of the s
pec, | 33 For CSS tests, you must also be sure you’re linking to a specific level of the s
pec, |
| 34 generally the first level where the feature being tested is defined. Where possi
ble, | 34 generally the first level where the feature being tested is defined. Where possi
ble, |
| 35 it’s preferable to link to the official version of the spec, which will start wi
th | 35 it’s preferable to link to the official version of the spec, which will start wi
th |
| 36 http://www.w3.org/TR/. This can usually be found as the ‘Latest version’ link in
the | 36 http://www.w3.org/TR/. This can usually be found as the ‘Latest version’ link in
the |
| 37 spec itself and will include the level of the spec in the URL. For example, the
proper | 37 spec itself and will include the level of the spec in the URL. For example, the
proper |
| 38 link to level 1 of the CSS Flexbox spec is: | 38 link to level 1 of the CSS Flexbox spec is: |
| 39 | 39 |
| 40 http://www.w3.org/TR/css-flexbox-1/#RELEVANT_SECTION | 40 http://www.w3.org/TR/css-flexbox-1/#RELEVANT_SECTION |
| 41 | 41 |
| 42 When testing features not yet available in an official draft, link to the approp
riate | 42 When testing features not yet available in an official draft, link to the approp
riate |
| 43 Editor’s Draft found at http://dev.w3.org/csswg/. Be sure to include the level o
f the | 43 Editor’s Draft found at https://drafts.csswg.org/. Be sure to include the level
of the |
| 44 specification in the link. For example, the proper link to the CSS Flexbox Level
1 | 44 specification in the link. For example, the proper link to the CSS Flexbox Level
1 |
| 45 Editor’s Draft is: | 45 Editor’s Draft is: |
| 46 | 46 |
| 47 http://dev.w3.org/csswg/css-flexbox-1/#RELEVANT_SECTION | 47 https://drafts.csswg.org/css-flexbox-1/#RELEVANT_SECTION |
| 48 | 48 |
| 49 Contributing | 49 Contributing |
| 50 ------------- | 50 ------------- |
| 51 | 51 |
| 52 Absolutely everyone is welcome (and even encouraged) to contribute to test | 52 Absolutely everyone is welcome (and even encouraged) to contribute to test |
| 53 development, so long as you fulfill the contribution requirements detailed | 53 development, so long as you fulfill the contribution requirements detailed |
| 54 in the [Contributing Guidelines][contributing]. No test is too small or too | 54 in the [Contributing Guidelines][contributing]. No test is too small or too |
| 55 simple, especially if it corresponds to something for which you've noted an | 55 simple, especially if it corresponds to something for which you've noted an |
| 56 interoperability bug in a browser. | 56 interoperability bug in a browser. |
| 57 | 57 |
| (...skipping 24 matching lines...) Expand all Loading... |
| 82 | 82 |
| 83 Please note that although we will grant write access directly to the Mercurial | 83 Please note that although we will grant write access directly to the Mercurial |
| 84 repo, it is strongly advised to use GitHub for test submissions to enable | 84 repo, it is strongly advised to use GitHub for test submissions to enable |
| 85 reviewers to use its built-in review tools. Direct submissions to Mercurial | 85 reviewers to use its built-in review tools. Direct submissions to Mercurial |
| 86 should be limited to administrative or housekeeping tasks, very minor changes | 86 should be limited to administrative or housekeeping tasks, very minor changes |
| 87 that don't require a review, or from advanced users of the system. | 87 that don't require a review, or from advanced users of the system. |
| 88 | 88 |
| 89 [contributing]: https://github.com/w3c/csswg-test/blob/master/CONTRIBUTING.md | 89 [contributing]: https://github.com/w3c/csswg-test/blob/master/CONTRIBUTING.md |
| 90 [github101]: http://testthewebforward.org/docs/github-101.html | 90 [github101]: http://testthewebforward.org/docs/github-101.html |
| 91 [speclinks]: http://testthewebforward.org/docs/test-templates.html#specification
-links | 91 [speclinks]: http://testthewebforward.org/docs/test-templates.html#specification
-links |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1313623003:
update-w3c-deps import using blink 9387ce8f51ec55db958c7429162d9be7d7c17123: (Closed)
Base URL: https://chromium.googlesource.com/chromium/blink.git@master