| commit | 56eea69b2496a1c2f6e70c1d665bd5ff08424466 | [log] [tgz] |
|---|---|---|
| author | Andreu Botella <abotella@igalia.com> | Fri Jul 12 04:57:31 2024 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Fri Jul 12 07:18:56 2024 |
| tree | 20caecdad84fb9131257686a8361c9dc8a4bc199 | |
| parent | ce8be753c342569470b92d416ff232e0805892a2 [diff] |
[line-clamp] [RubyLB] Make sure ruby isn't visible in clamped lines With RubyLB, in some cases ruby annotations would not be hidden even though the line containing them would be. This is because when a line is after the clamp point, the line box and its logical line items would be marked as hidden for paint, but in RubyLB the line's ruby annotations and their line items are stored in the logical ruby columns. This patch fixes this in `FragmentItemsBuilder::AddLine`, when `FragmentItem`s are created for a line's multiple annotations, by marking every item in the annotations as hidden for paint if the line's fragment is marked as such. Aside from adding a test for this issue, this patch also adds a test that the sizing of a clamped block box properly takes into account any ruby annotations that add leading to a line. This already worked as expected, presumably due to https://crrev.com/c/5683304 storing the `PreviousInflowPosition` at the clamp point, but the effect on ruby had not been tested in that CL. Bug: 40336192 Change-Id: I95fe796bb887d1d205dd43c2644095b6c6f225e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5695646 Reviewed-by: Kent Tamura <tkent@chromium.org> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Andreu Botella <abotella@igalia.com> Cr-Commit-Position: refs/heads/main@{#1326551}
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!