commit | b2ae596c5fe3bdae2eea47d59d50e517dc054737 | [log] [tgz] |
---|---|---|
author | Jordan Taylor <jortaylo@microsoft.com> | Fri Sep 10 20:40:57 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri Sep 10 20:57:21 2021 |
tree | a18a10d1eb7c425743e8dada152e08f761369fdf | |
parent | c950ef462d1013be30df1a7df742001283b54177 [diff] |
Relanding: Integrated Progress based animations with CSS Animations This is a relanding of: https://chromium-review.googlesource.com/c/chromium/src/+/3130703 The only differences between this CL and the original is removal of a time-range related test case and the change in: third_party/blink/web_tests/external/wpt/scroll-animations/current-time-root-scroller.html The fix was to add a single frame in between creating the timelines and trying to access them. This method is also used in many other existing tests. Original description: Timeline duration can now be stored on an AnimationEffect. This was needed since for CSS animations, InertEffects with no owning animation are used until later in the pipeline. Normally the owning animation of an effect is used to gain access to the corresponding timeline which provides the timeline duration needed for timing normalization math, but in some cases the duration was needed before an effect had an owner assigned. As such it is now possible to create an InertEffect and pass in a timeline duration if needed. Added logic for when CSS animations swap from progress based timeline to a time based timeline. This new logic preserves the current progress of the animation even when current times do not match up. I also removed time range from some CSS tests since they are now supported by progress based animations. Bug: 1216655, 1140602, 1243947 Change-Id: Ibec9437c1027702b888e8bab65f890687054e3be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3142895 Reviewed-by: Kevin Ellis <kevers@chromium.org> Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Jordan Taylor <jortaylo@microsoft.com> Cr-Commit-Position: refs/heads/main@{#920356}
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!