commit | e3d1836de35ba784549c9ab98fef6de57646af55 | [log] [tgz] |
---|---|---|
author | David Bokan <bokan@chromium.org> | Wed Apr 13 15:55:07 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Apr 13 16:09:02 2022 |
tree | 632c90154c59f2aa2530368f61e31928e0233c00 | |
parent | b2aeec05d753c742ea35b4cc395d52b4b168245b [diff] |
Bubble scrollIntoView from position:fixed in frame LayoutBox::ScrollRectToVisibleRecursive was erroneously stopping the recursion once it reached a position:fixed element, assuming that further recursion to the parent was unnecessary. This is true for the main frame; however, in an iframe, the element is only fixed to its frame's scroll offset. Ancestor scrollers of the frame can still affect the target element's position so scrolling should continue with them. The behavior is that once a position:fixed element is reached, the recursion should continue from its frame's parent. This CL also takes the opportunity to clean up the ScrollRectToVisibleRecursive method to make the logic clearer and iterative rather than recursive. The LayoutBox version of ScrollRectToVisible is now solely to walk up as high as it can in the layout tree of the local frame root. Crossing IPC boundaries is performed by LayoutObject. The only caller that doesn't go through LayoutObject is Autoscroll but that latches to a single scroller and doesn't bubble at all so isn't a concern. See also: https://github.com/w3c/csswg-drafts/issues/5492 Bug: 1019427 Change-Id: I336866b927431c2faf2b645474dd32cd1771bb78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3579486 Reviewed-by: Daniel Libby <dlibby@microsoft.com> Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/main@{#992062}
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!