commit | 431117b4651e2ca79a6febb461724ba54f79a9e5 | [log] [tgz] |
---|---|---|
author | Daniel Holbert <dholbert@cs.stanford.edu> | Wed Mar 29 14:30:04 2023 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Thu Mar 30 08:30:08 2023 |
tree | 6f62f887e29298b05715b46e94acd960968537ff | |
parent | 7e34f805c430fea043633d1a2fc6c8635748143a [diff] |
Use Ahem font to avoid antialiasing-related fuzzy test-failures in WPT clip-path-text-*.svg Before this patch, these tests compare the string "CLIP" used as a green rect's clip-path, with the reference case just being plain green text. Unfortunately, there's no guarantee that the text's antialiased fringes will produce precisely the same rendered result, when comparing these two modes of rendering; so this setup can produce some spurious test-failures, with large numbers of mismatching pixels along the antialiased edges of the characters. The Ahem font can help here, by reducing the amount of curves and antialiasing, and by removing the choice-of-default-font as a source of cross-browser & cross-platform variability in these tests. So: this patch switches these tests to use the Ahem font, with a reduced font-size (and standard font-weight) to keep the string approximately the same length. I've also adjusted the text's y-position in some of the tests (the "text-over-a-polygon" tests), so that it's easier to visually distinguish the bar of Ahem text from the polygon. I've also changed the test to use "X" as the only rendered character, since it's specially defined to produce a square glyph, per https://web-platform-tests.org/writing-tests/ahem.html With this patch, these tests pass in Firefox, with no fuzzy annotation required. Differential Revision: https://phabricator.services.mozilla.com/D173917 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1824284 gecko-commit: 0c3c34be4ef78205dac4bc27fd63addacca935ea gecko-reviewers: longsonr
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!