commit | 2181d00ec2c4f91be714a025cd60690b4e5f233c | [log] [tgz] |
---|---|---|
author | Koji Ishii <kojii@chromium.org> | Mon Apr 12 09:58:58 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Apr 12 10:18:59 2021 |
tree | c9f0c8b73e40504640d5c2e6a173c1722871ec03 | |
parent | 9353d550f0d49f5fd090dc276b60528c642b80d0 [diff] |
Make size-adjust-01 more focus on `size-adjust` This patch makes the following test more focus on testing the `size-adjust` descriptor by eliminating dependencies to other parts of the spec: external/wpt/css/css-fonts/size-adjust-01.html Before this change, the test had: ``` @font-face { font-family: large-font; unicode-range: U+41-5A; /* Uppercase ASCII only */ } .large { font-family: large-font, sans-serif; } ``` In CSS, the [first available font] is defined as: [first available font]: https://drafts.csswg.org/css-fonts-4/#first-available-font > the first available font that would match the U+0020 (space) > character which was further clarified in https://github.com/w3c/csswg-drafts/issues/4796: > RESOLVED: The first available font is the first available > font in the font-family list whose unicode-range includes > the space character From these, the [first available font] of the `.large` in the test is `40px sans-serif`, while it is `60px sans-serif` in the reference. The current CSS does not define the exact baseline position when multiple fonts are used as the result of cascading. Blink uses the metrics from the [first available font], making this test fail to match the reference. This patch adds U+20 to the `@font-family`, to make it the [first available font]. Bug: 1196631 Change-Id: I8de5b8a1ef22ffde5c791164c8183e17264c14c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2817869 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Dominik Röttsches <drott@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#871419}
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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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 http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
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!