commit | eba3c32a20388ad2fe560d27dc08999ace4b96f2 | [log] [tgz] |
---|---|---|
author | L. David Baron <dbaron@chromium.org> | Thu Oct 21 18:36:58 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Oct 21 18:45:32 2021 |
tree | c490d371d6542fcd3f103d349a77d9f776c4629a | |
parent | dfa1341d12fa7ef3645ceb63d9382539b7995336 [diff] |
Fix 2 test expectations in rotate-composition.html. I previously adjusted the expectations for this test in https://crrev.com/19620452a45a851f38799bcc2bd5ddb9d5b120ac . However, I believe these two expectations were incorrect both before and after that adjustment, and the behavior shown in both Chromium and Gecko is correct. (WebKit differs slightly by producing 'none' rather than '0deg'.) I think this is correct because we're interpolating between two transforms: (a) '1 2 3 360deg' (the result of an add) (b) '0 1 0 100deg' Since the normalized axes differ, this interpolation falls into the rules for interpolation of matrices, as described in https://drafts.csswg.org/css-transforms-2/#interpolation-of-transform-functions . (The rules for the 'rotate' property incorrectly say that SLERP is always used, but I think that should be fixed to match the rules for the rotate() function. Either way, however, this test expectation should be based on interpolation of matrices using SLERP.) Since the matrix for (a) is the identity matrix, and the progress of the interpolation is at 0, the result is the identity matrix, which should (although the spec should make this explicit) be represented as 0deg. This should be fixed in https://github.com/w3c/csswg-drafts/issues/4516 . Bug: 1180834 Change-Id: I0a5e15535da56949fc88bdf48423b41d409fe290 Fixed: 1006239 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3237448 Auto-Submit: David Baron <dbaron@chromium.org> Reviewed-by: Kevin Ellis <kevers@chromium.org> Commit-Queue: Kevin Ellis <kevers@chromium.org> Cr-Commit-Position: refs/heads/main@{#933958}
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!