commit | 22bf1f9e0ed1f729fb91632c39b2c8d68844f503 | [log] [tgz] |
---|---|---|
author | Philip Rogers <pdr@chromium.org> | Mon Nov 15 23:40:57 2021 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Nov 15 23:48:34 2021 |
tree | bf39509c7a9c3fba8a8895d86b80e942cd5a3913 | |
parent | 1cdd682a491f3301445ee0dadc312bf53b2ae851 [diff] |
Do not skip compositing update for non-animation transform changes Properties like "will-change: transform" are direct compositing reasons which let us skip raster when properties change. Usually, we still need to update compositing when directly-composited transforms change because overlap can change. An exception to this is animations which assume worst-case overlap in |PendingLayer::VisualRectForOverlapTesting|. This patch stops skipping the compositing update for non-animation transform changes. An alternative approach of assuming worst-case overlap for will-change transform was investigated in https://crrev.com/c/3280439 but this has two downsides: complexity and compositing memory (a good example is composited-scroll-overlap-test.html). Before CompositeAfterPaint, we would need to run compositing as well, so the approach in this patch has precedent. We may want to expand the visual rect for will-change: transform in the future, for performance parity with animations. Bug: 1267689 Change-Id: I9812426e9a159bdbe44476390e10fe53478f9ccc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3282945 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/main@{#941904}
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!