commit | d23351753bfb2c7757b9fe2470bbcf2801a66c23 | [log] [tgz] |
---|---|---|
author | Alison Maher <almaher@microsoft.com> | Wed Apr 06 17:23:54 2022 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Apr 06 17:42:31 2022 |
tree | 5d5c9dea8a61860532a6480967d758d116a2ea94 | |
parent | 31c378630a0dcbb9f1adac6f343760b354d984bd [diff] |
[LayoutNG] Fixedpos in abspos in inline container A fixedpos nested in a fragmented OOF would crash when its CB was an inline because we would set the fixedpos_containing_block of the OOF ancestor to the inline. However, the containing block should not be set to an inline, but rather to the closest parent block flow of the inline. To fix this, add a new member to the OOF node to keep track of a fixedpos_inline_container and set the fixedpos_containing_block once the fixedpos_inline_container's parent block flow is reached. This allows us to make use of the same logic for handling inline CBs as we would for normal un-nested OOFs. The same issue also occurs for nested multicols, so relevant crashing tests have been added and a similar fixedpos_inline_container member was added to NGMulticolWithPendingOOFs. Ref tests were not added as a part of this CL, although I suspect the relative offset logic might be off. TODO added to investigate this separately. Bug: 1312790 Change-Id: I236006a74e8917745cbaacbe51fc71b7e393f11b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3573056 Reviewed-by: Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/main@{#989483}
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!