commit | 2817af77c7e8465130e93b5d4935e0887dd8ea81 | [log] [tgz] |
---|---|---|
author | David Awogbemila <awogbemila@chromium.org> | Thu Mar 14 21:08:22 2024 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Mar 14 21:40:48 2024 |
tree | 8d013782a5df0765527631e3c34fed4457e2d92e | |
parent | b83bbdfc87212d5af05a3b0e0dd82c4fdf7031c1 [diff] |
[css-scroll-snap-2] Switch snapchanged to updated SnapEvent interface This patch makes snapchanged fire SnapEvents based on the updated[1] SnapEvent interface which supplies exactly one snap target per axis. We detect that the snap targets of a SnapContainerData has changed by comparing its current target_snap_area_element_ids_ to the element ids that were most recently used to evaluate snapchanged. This requires that if a snap container is snapped in both axes but is then scrolled in only one axis, it needs to remember what it was snapped to in the other (unscrolled) axis - previously, we simply forgot what we were snapped to in the unscrolled axis. prefer-common-to-both-axes.html had to be modified because remembering what we are snapped to in the unscrolled axis affects the choice of snap targets when there is a layout change resulting in the targets along each axis not being mutually visible. Currently, chromium handles this somewhat arbitrarily (This will be adddressed in crbug.com/329250094) This patch gets around this by scrolling in both axes. snapchanged-ensures-dom-order.html is deleted because we don't return a list anymore so we don't need to ensure the order of the list. [1]https://github.com/w3c/csswg-drafts/pull/9515 Bug: 329111147 Change-Id: I4af884bd58d0517087a8c8960bf7646f3a36ba72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5369681 Reviewed-by: Steve Kobes <skobes@chromium.org> Commit-Queue: David Awogbemila <awogbemila@chromium.org> Cr-Commit-Position: refs/heads/main@{#1273041}
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!