commit | 644aba8746b83668d5d9033cda16ae3f8bba0b3d | [log] [tgz] |
---|---|---|
author | Antoine Quint <graouts@apple.com> | Thu Jun 16 13:15:22 2022 |
committer | GitHub <noreply@github.com> | Thu Jun 16 13:15:22 2022 |
tree | 22e806e496afd92182090db1ecb0e7a01169a542 | |
parent | d387101095115f28446dbf2da77fb64dea697815 [diff] |
Split testing CSS transitions before load vs. load event behavior when changing <img>.src The test css/css-transitions/before-load-001.html relies on loading an image where the load is set to 100 seconds such that the window `load` event dispatch is delayed until a CSS Transition is ran. At that point, the image's source is set to the empty string to stop the image load and have the window `load` event dispatched. Safari has an issue where an <img> pointing to a long-loading resource will continue delaying dispatch of the `load` event on the window even when the image source has been reset. This issue is tracked by https://bugs.webkit.org/show_bug.cgi?id=241676. As a result, css/css-transitions/before-load-001.html causes a harness timeout in Safari even though the ability to run a CSS Transition before the window `load` event has been dispatched works correctly and the test assertions pass. We work around that issue by lowering the load duration for the image to 1 second instead of 100. This doesn't changed the functionality that this test is explicitly testing. And to explicitly test that resetting a long-loading image source no longer delays the dispatch of the window `load` event, a new dedicated test is added, which will itself cause a timeout in Safari, but that is what is expected. Addresses https://github.com/web-platform-tests/wpt/issues/34444.
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!