commit | 5e226302de42f1c3679ba0c265b59cbc81a20af7 | [log] [tgz] |
---|---|---|
author | Mats Palmgren <mats@mozilla.com> | Mon Nov 01 15:04:29 2021 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Mon Nov 01 22:24:18 2021 |
tree | 4180457f2b0426356830eaee2c357e5b6840f50a | |
parent | 351ee5a248ffe59bd618c96a13efac503e829595 [diff] |
Update various counter style tests to not assume that a range is applied. DONTBUILD In particular, for 'hebrew', the spec says: "Implementations must implement hebrew at least to the range specified in the @counter-style rule above, but may implement it to a higher range." at https://drafts.csswg.org/css-counter-styles/#ref-for-hebrew%E2%91%A0 and for CJK: "Because opinions differ on how best to represent numbers 10k or greater using the longhand CJK styles, all of the counter styles defined in this section are defined to have a range of -9999 to 9999, but implementations may support a larger range." at https://drafts.csswg.org/css-counter-styles/#complex-cjk Firefox and Chrome (at least) do implement a larger range than the spec recommends, so there needs to be an alternative reference for these tests to make them pass (which is OK since the range isn't normative). Differential Revision: https://phabricator.services.mozilla.com/D129898 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1738356 gecko-commit: 2be753dcd9255d47d78429a71db94a4fc50a1f4b gecko-reviewers: hiro, TYLin, saschanaz
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!