commit | 21dc7156fbd1e6a6e24eece7a1159e1c1913560d | [log] [tgz] |
---|---|---|
author | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Oct 25 17:03:30 2023 |
committer | GitHub <noreply@github.com> | Wed Oct 25 17:03:30 2023 |
tree | 5bd2edcb9071228cbc0a5cc879f3cbb9d192f61d | |
parent | ae3d6e3e0e7121408c173e158fb9eab53ec29b88 [diff] |
view-transition: Move pagereveal tests to WPT (#42669) The `pagereveal` event will be specified and shipped separately from view transitions so move tests into WPT. Since the spec is still WIP these tests are marked tentative for now. Tests that were specifically dealing with usage of the `viewTransition` attribute and its behavior in relation to a view transition were left in the wpt_internal directory for view-transitions since those seems specific to that feature. Review note: PS#1 moves the files, diff from it to see changes. These tests need to run in the no-forced-frame-update virtual test suite since they're testing event order before rendering begins. WPT tests run in single-threaded-mode which does not prevent scheduling frames before rendering begins. This suite was added for other similar tests. Additionally, there is a race during prerender activation between a SynchronousComposite being called and receiving the WasShown signal from the RenderWidgetHost. If the test invokes SynchronousComposite before WasShown the BeginMainFrame is aborted. If a test is waiting on e.g. a requestAnimationFrame it will timeout. This CL fixes this by detecting this situation and scheduling a new frame when the widget becomes shown. Bug: 1466250 Change-Id: I218f5ed18bbbf0a1c176fbf562aa5ae939a3adcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4956092 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by: Khushal Sagar <khushalsagar@chromium.org> Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1214522} Co-authored-by: David Bokan <bokan@chromium.org>
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!