commit | b281a06110c196a820b789201ab8793bbef0219a | [log] [tgz] |
---|---|---|
author | Fredrik Söderquist <fs@opera.com> | Tue Nov 19 17:30:05 2019 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Nov 19 17:45:02 2019 |
tree | e06eca88f286645cd3f065129b9eeee609ec95b4 | |
parent | 4d9264980b9e960d0c966402d747a545fa16fb76 [diff] |
Use existing external resource for <use> while revalidating When we load a previously cached resource for <use> and it requires revalidation - and an earlier <use> that references the same resource hasn't yet generated its shadow tree - we could end up failing to generate a shadow tree for the the "first" <use> since the resource appears to be "invalid" while the revalidation is in progress. This "first" <use> would then not be invalidated when the revalidation completes. Consider the resource to be valid while revalidating if it has a Document already - meaning it has previously finished loading and successfully parsed a document. This means the "first" <use> might end up being stale until it's invalidated if the revalidation returned a newer version of the resource - which is wrong but arguably better than failing to display at all like was the case previously. (This should also be consistent with how other types of resources are handled in cases like this.) Bug: 593261, 1021530 Change-Id: I9d68a1a60685757a990c2ec811c5ca53afc4fb25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903200 Commit-Queue: Fredrik Söderquist <fs@opera.com> Reviewed-by: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#716678}
The web-platform-tests Project is a W3C-coordinated attempt to build 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!