commit | 2d43f11735ea65ed14bd3bb86248cf4ffa0f2cdb | [log] [tgz] |
---|---|---|
author | Dominik Röttsches <drott@chromium.org> | Wed Mar 25 12:52:25 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Mar 25 13:18:18 2020 |
tree | d34dba8ad1edf8b34baaf810e1acb2cda0e945f1 | |
parent | a061b2da77ab3c9010ef8afcbc3830773c9dbb5c [diff] |
Allow specifying variable font range descriptors in either direction Style, stretch and weight descriptor allow specifying ranges for the variable font that the src: descriptor is referencing. The range definitions allow both the smaller or larger value to go first and need to be swapped by the UA. Keep range value lists in reversed order in the computed style, but swap them in the FontFace implementation to become meaningful values.This keeps serialisation intact as specified in the @font - face declaration( as opposed to reversing the list at the CSS parsing level) and matches Firefox' behaviour. Adjust test expectations in at-font-face-descriptors.html for bounds out of order test cases: expect out of order bounds to be returned in order as specified. Test case was previously failing in all browsers [1] - with this change it will pass in Chrome and Firefox. Mark font-parse-numeric-stretch-style-weight.html test case "500 400 matches 500 400 for weight in @font-face" as passing in Chrome. [1] https://wpt.fyi/results/css/css-fonts/variations/at-font-face-descriptors.html?label=master&label=experimental&aligned&q=css%2Fcss-fonts%2Fvariations%2F Fixed: 1063867 Change-Id: I5ae7bc5f3e3a75fa9dce09ca0a66dd083ef29b0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2116447 Commit-Queue: Dominik Röttsches <drott@chromium.org> Reviewed-by: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#753192}
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.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.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
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!