| commit | 6d47de037a4b85f083582061ae846a872bc53ee4 | [log] [tgz] |
|---|---|---|
| author | Anders Hartvoll Ruud <andruud@chromium.org> | Mon Sep 05 14:02:44 2022 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Sep 05 14:20:35 2022 |
| tree | 83f14a96a0dd72d6b1006add54c6783302df3e3a | |
| parent | 249e1eb8e6542731f41738ab11def2aae4548375 [diff] |
[scroll-animations] Determine forced updates using style roots For forced style updates on a single element (e.g. getComputedStyle), we try to avoid updating the style and layout-tree if we know that the next call to UpdateStyleAndLayoutTree will not affect that element. Figuring this out involves traversing the ancestor chain of the target element, looking for dirty-flags and the like. However, with the introduction of scroll-timelines, it is no longer sufficient to traverse the ancestor chain, because the named timeline lookup can reach previous siblings (and previous siblings of all ancestors). We probably don't want to traverse all of those siblings, so instead this CL suggests basing the optimization on whether or not there is a style recalc/invalidation root in the ancestor chain. This makes it possible to solve the problem of scroll-timelines/ siblings by checking the parent element of the style root against the the parent of the target element. Bug: 1317765 Change-Id: Ic13587ce7535da02aeb00699e29c26ee867eb249 Fixed: 1356493 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3859628 Reviewed-by: Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/main@{#1043196}
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!