commit | 4b8ff663ac0796509a904e74bae49ca734c869d9 | [log] [tgz] |
---|---|---|
author | Morten Stenshorne <mstensho@chromium.org> | Tue Apr 26 13:38:07 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Apr 26 13:48:43 2022 |
tree | 020b1c04ed71ed23fdc6dc329009590c39fa5de5 | |
parent | e8199c0728bb283d72cfca4986751d72e4ecf80d [diff] |
Prevent parallel flows around column spanners. If there is a column spanner inside a container that we're past (due to restricted block-size), we cannot let this container establish a parallel fragmentation flow [1], as that could result in laying out nodes that are defined after the container (and therefore after the spanner) *before* the spanner. Such nodes would generate fragments *before* the spanner, and then restart again after the spanner. This used to cause major confusion in code that expects the fragments associated with the LayoutBox to be in sync with the fragments actually produced. In addition to addressing fragment structure inconsistency (which caused security bugs and lots of DCHECK failures), this also fixes some correctness issues. During layout we'll now create a chain of ancestors between the multicol container and the spanner, so that we in subsequent layout passes can tell whether we need to prevent parallel flows or not on a given node. We may even have to repeat the initial column balancing pass because of this: If there are forced breaks, we may enter a parallel flow incorrectly because we didn't know about the spanner. [1] https://www.w3.org/TR/css-break-3/#parallel-flows Bug: 1314998, 1309859 Change-Id: I7d88a8a4f29b5c55631477f21029ade7a8c0cc20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3599047 Reviewed-by: Koji Ishii <kojii@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#996130}
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!