commit | 4409e07e970e6fd735944c0f60ab6678d2a1bb1f | [log] [tgz] |
---|---|---|
author | Oriol Brufau <obrufau@igalia.com> | Mon Jul 27 15:03:21 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jul 27 15:03:21 2020 |
tree | 6cde9ee0f004ab43b2ed809d5df8518644c05513 | |
parent | 6e6c7b4f23eb3d87246a80068b846d69efea6420 [diff] |
[css-pseudo] Support text-transform in ::marker In https://github.com/w3c/csswg-drafts/issues/4206, the CSSWG resolved that the 'text-transform' property should apply to ::marker, and that by default it should be set to 'none' in the UA stylesheet. This patch implements these changes. Note that setting it to 'none' is an observable change in LayoutNG, since it prevents the ::marker from inheriting the 'text-transform' of the list item. This was considered a better behavior by the CSSWG, and it's the behavior that legacy layout already had. LayoutListMarker, used for ::marker with 'content: normal' in legacy layout, doesn't implement the marker text as actual text. Therefore, 'text-transform' has no effect. Bug: 1031667 TEST=external/wpt/css/css-pseudo/marker-default-styles.html TEST=external/wpt/css/css-pseudo/marker-text-transform-default.html TEST=external/wpt/css/css-pseudo/marker-text-transform-uppercase.html TEST=external/wpt/css/css-pseudo/parsing/marker-supported-properties-in-animation.html TEST=external/wpt/css/css-pseudo/parsing/marker-supported-properties.html TEST=http/tests/devtools/elements/styles-2/pseudo-elements.js Change-Id: I2c2b554f521139fabb502856fedc6230aa45c787 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2315872 Reviewed-by: Koji Ishii <kojii@chromium.org> Commit-Queue: Oriol Brufau <obrufau@igalia.com> Cr-Commit-Position: refs/heads/master@{#791815}
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.
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.