| commit | 7f913d9d12a54858ffc04ac18b262d775e19184a | [log] [tgz] |
|---|---|---|
| author | Chris Harrelson <chrishtr@chromium.org> | Thu Jun 10 16:40:21 2021 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Jun 10 16:59:13 2021 |
| tree | 7d2346e24825372a3ce5255cb964102c6646c1a6 | |
| parent | 73667b91586d95a3387e6ef83e3ec9dcea5e2fff [diff] |
[CLS] Allow for shifts in root-relative coordinates for scroll anchoring Currently, layout adjustments plus scroll anchoring may result in all three of the following happening in the same rendering update: * Layout changes that moves a tracked element relative to its layout shift root (e.g. via content-visibility changing skip state, but it could also be any layout change offscreen) * Natural scroll via a user gesture that visually moves the element visually on-screen * Scroll anchoring to counter the layout change, but not the natural scroll We currently do not handle that case. We only handle the case of a layout change that is directly counter-balanced by a scroll, or a pure scroll. This CL serves the above use case by plumbing the value of the scroll anchor scroll to LayoutShiftTracker, and early-outing if the root- relative position of the before and after rects are equal, once scroll anchoring is taken into account. Bug: 1215368 Change-Id: I8a5240603cebf3a78dfc4fa82b4839cf1af68800 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2946459 Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#891250}
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:
#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.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.
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.
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!