commit | 94b37f7624fb523c15cdd581755a2556ddd2b65b | [log] [tgz] |
---|---|---|
author | Rune Lillesveen <futhark@chromium.org> | Thu Dec 07 13:18:02 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Thu Dec 07 13:36:08 2023 |
tree | 0091050b8e050b48df665b3a7acb247706640806 | |
parent | 00dee68a67459b04b971f928c7360cb1be036613 [diff] |
Missing ::first-letter style update for size queries Style for ::first-letter pseudo elements are updated as late as possible to allow nodes to re-attach to make sure any first-letter text node changes are included when computing style for the first rendered letter. When the StyleRecalcChange were already marked for ReattachLayoutTree() when reaching the ::first-letter update, we assumed some ancestor of the ::first-letter element would be re-attached, and the ::first-letter style being updated in Element::AttachLayoutTree() for the originating element. But, if the originating element was a size container, and we skipped style recalc for its descendants, we would mark the stored StyleRecalcChange for re-attachment of the children when resuming, even if the originating element itself would be re-attached. Instead, check that we also did not suppress style recalc for the originating element for the ::first-letter before skipping its style update during style recalc. Bug: 1505250 Change-Id: I8d45c219e0d8c2a2d8ab6e0ec6149d9f34366fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5097303 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1234442}
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!