commit | 50cb5c61433c4b554b17ad6baf6c4a8234bdadcd | [log] [tgz] |
---|---|---|
author | Lingqi Chi <lingqi@chromium.org> | Tue Nov 26 14:48:04 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 26 14:48:04 2024 |
tree | 100eab5562457cbee3da451abc469bcd0d8d8e22 | |
parent | 0b2925ee441b19784a1060090b82a3554bccb696 [diff] |
[text-box-trim] Retire text-box-edge propagation restriction We added a restriction that the effective text-box-edge can be propagated to its child only if the same node defines a non-initial text-box-trim value when text-box-edge is not inherited. But now the specification is updated[1] which marks text-box-edge as inherited, and we no longer need this restriction. This CL also removes text-box-trim/text-box-trim-ignore-nested-text-box-edge.html from the web-test. This test was replaces by text-box-trim-not-ignore-nested-text-box-edge.html (each test disagrees with the other) since [2], but for some reasons still stays at the wpt codebase. A follow-up will retire the EffectiveTextBoxEdge field. [1] https://github.com/w3c/csswg-drafts/issues/10904 [2] https://github.com/web-platform-tests/wpt/commit/288ee9d3430ff09a227f1c96b3cbb25170ab1af4 Bug: 367766472, 374787320, 40254880 Change-Id: I789136ef54fa2d0c8b7a97b08caf1217512d10c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6038647 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/main@{#1388218}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.