commit | e652518e6f5d1392035eb435775765d8271d581e | [log] [tgz] |
---|---|---|
author | Morten Stenshorne <mstensho@chromium.org> | Fri Jun 26 14:09:39 2020 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri Jun 26 14:31:19 2020 |
tree | 651d5b4115b17d39d6e10eccf856e7f0e480cff0 | |
parent | b6a67998c6c2827319726af3bea65e572b5a125a [diff] |
[LayoutNG] Unbreakable content may affect container size. If there's something unbreakable inside a container at a fragmentainer boundary, and there are no possible breakpoints, it will overflow the fragmentainer. This was already working, but in such cases, the container should then also overflow the fragmentainer (and consume the amount of space that it overflows). This will also effectively make us refuse breaking inside the block-start border or padding area (since that's included in the intrinsic block-size, which is unbreakable). The fieldset layout algorithm is still able to handle breaks inside borders and padding (and had tests for it), but since this will no longer happen, some tests had to be updated. The algorithm should also be fixed (only a TODO for now), to no longer support such breaks (mostly about removing a little code). There's also a fieldset-specific regression introduced by this CL: crbug.com/1097012 . This is about fieldset block-end padding and how the fragmentation machinery gets confused by it. This affects two unit tests. Rather than disbling them, I thought it was better to update with incorrect expectations (with a TODO), since the tests are probably still useful, even with this bug. Bug: 829028, 875235 Change-Id: I833faf7bc84328d36c9ccd640478badfd6278492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2263353 Reviewed-by: Alison Maher <almaher@microsoft.com> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#782953}
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:
#testing
on irc.w3.org; includes participants located around the world, but busiest during the European working day; all discussion is archived hereIf 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 http://w3c-test.org/.
Pull requests are automatically mirrored except those that modify sensitive resources (such as .py
). The latter require someone with merge access to comment with “LGTM” or “w3c-test:mirror” to indicate the pull request has been checked.
In the vast majority of cases the only upstream branch that you should need to care about is master
. If you see other branches in the repository, you can generally safely ignore them.
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!