commit | bfe011aa848f680dc28a4c353bd51e08caffb757 | [log] [tgz] |
---|---|---|
author | Morten Stenshorne <mstensho@chromium.org> | Thu May 05 14:40:15 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu May 05 14:53:47 2022 |
tree | 139ab31fc3d3b54d7968115d393e0849e2053f10 | |
parent | 541e49a74546de0128524f7e97906d24b3cfdefa [diff] |
Simplify fragment / break token copying when adding OOFs. There were two known problems, that the code didn't handle. 1. We may have generated a fragment for a node which is preceded by a node that generated a break token. See break-after-oof-before-preceding-pushed-float-crash.html 2. Clearance may push a node past multiple fragmentainers (with a break-before break token in each fragmentainer). The code would get confused when it found these break tokens while expecting an incoming OOF break token. I started by fixing these separately, but realized that we might as well just remove the special child fragment / break token iteration code. All we need is making sure that we keep the order of child fragments and break tokens from the original fragment intact. Furthermore, we don't need to propagate any break tokens for OOFs that break, since NGOutOfFlowLayoutPart will resume them correctly anyway. Note that we still need the break tokens associated with the OOF fragments (for pre- paint); it's just that we don't need to propagate them up to the fragmentainer, since layout doesn't need it. Add a flag to the container builder, to prevent outgoing break tokens from being added automatically when adding child fragments. Perform these two steps separately in NGSimplifiedOOFLayoutAlgorithm(). Bug: 1318455 Change-Id: I8930a78754f0695fd5f99a74e0a5f7ef363fb0f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3622335 Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#999878}
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!