commit | 5a160eb77cad3759c55a15a130e974c30e215d99 | [log] [tgz] |
---|---|---|
author | Sammy Gill <sammy.gill@apple.com> | Tue Dec 19 17:56:53 2023 |
committer | GitHub <noreply@github.com> | Tue Dec 19 17:56:53 2023 |
tree | 7f78be224c71858a11e031562242940dac78da29 | |
parent | 1cea438aed9655c42ed5476912476eb221c04daf [diff] |
WebKit export of https://bugs.webkit.org/show_bug.cgi?id=266506 (#43719) This patch expands upon 272085@main which fixed a bug related to an interaction between grid layout and size containment. In particular, the patch allowed the grid track sizing algorithm to stretch auto sized tracks even during size containment. For the exact same reason we also want to relax the size containment constraint imposed upon the grid track sizing algorithm to allow it to perform portions of the "Expand Flexible Tracks," section. The only portion of this step we want to skip is when we are computing the flex fraction and the free space is indefinite, since this is the only part of this section that takes into consideration the grid's contents. To compute the flex fraction in this case, the spec says that it is the maximum of: - For each flexible track, if the flexible track’s flex factor is greater than one, the result of dividing the track’s base size by its flex factor; otherwise, the track’s base size. - For each grid item that crosses a flexible track, the result of finding the size of an fr using all the grid tracks that the item crosses and a space to fill of the item’s max-content contribution. During the size containment "Sizing as if empty," phase we can completely take into consideration the first computation, but we should not compute or consider the second. https://drafts.csswg.org/css-contain/#containment-size https://drafts.csswg.org/css-grid-2/#algo-flex-tracks
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!