commit | 2b9cfbf0c87d9d0130a0dfc5f2da3b81eb1b86be | [log] [tgz] |
---|---|---|
author | Morten Stenshorne <mstensho@chromium.org> | Fri May 06 07:56:59 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri May 06 08:10:52 2022 |
tree | 7c826a47d11e0729c3bce884e18d6a199d4b098f | |
parent | 08a1105af6d304b415f2c590f2ba231c7df41777 [diff] |
Always create an anonymous contents wrapper inside a fieldset. This way we'll have less to worry about in the layout algorithm. Padding handling was incorrect, and it caused an infinite loop, because the algorithm expected the anonymous child to take care of trailing padding, and therefore didn't pass it to FinishFragmentation(). We therefore failed to treat the trailing padding as monolithic. We need to treat padding as monolithic, or we might never get past it if it's taller than the fragmentainer (and push it ahead of us into the next fragmentainer infinitely). The fragmentation code would believe that we managed to fit some of it in one fragmentainer, but we'd in fact try again from the start of the padding-block-end in the next fragmentainer (because it should be monolithic, that's why!) - forever. Just making sure that there's always an anonymous contents wrapper simplifies things and fixes bugs, including a minor correctness bug; see the new test empty-scrollable.html Some unit tests had to be updated. These expectations were mostly last touched by CL:2960239 , which eliminated the need for anonymous content wrappers if the fieldset only had a legend child. Now we'll always create them. Bug: 1322426 Change-Id: I215ecd6387e388d0a6801476b6269cb8fb84cba3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3629580 Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/main@{#1000277}
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!