| Auto-Submit | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
lgtm w/a comment
// [ none | grow | shrink] && [ consistent | per-line | per-line-all]? &&
// <percentage>?The [`&&` operator](https://drafts.csswg.org/css-values-4/#comb-all) is "in any order", so you'll need a loop, like the one in [`TextIndent::ParseSingleValue`](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/css/properties/longhands/longhands_custom.cc?q=TextIndent::ParseSingleValue&ss=chromium).
Or, should the use of `&&` in the syntax be changed?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// [ none | grow | shrink] && [ consistent | per-line | per-line-all]? &&
// <percentage>?The [`&&` operator](https://drafts.csswg.org/css-values-4/#comb-all) is "in any order", so you'll need a loop, like the one in [`TextIndent::ParseSingleValue`](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/css/properties/longhands/longhands_custom.cc?q=TextIndent::ParseSingleValue&ss=chromium).
Or, should the use of `&&` in the syntax be changed?
Thank you for pointing it out.
I misunderstood `&&`. I want to start with a stricter syntax, and meant ordered components.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
4 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: third_party/blink/renderer/core/css/properties/css_parsing_utils.cc
Insertions: 1, Deletions: 1.
The diff is too large to show. Please review the diff.
```
FitText: Merge two properties into one
This CL removes `text-grow` and `text-shrink` properties, and introduces
the `text-fit` property that covers both functionalities.
New Property Syntax:
text-fit: [ none | grow | shrink]
[ consistent | per-line | per-line-all]?
<percentage>?
This CL doesn't change the last component from <length> to <percentage>.
It will be addressed in a following CL.
* blink::ComputedStyle had two blink::FitText instances. Now it has
a single blink::FitText, and blink::FitText has a type field of
which value is kNone, kGrow, or kShrink.
* wpt_internal/css/fit-width-text/
text-shrink-valid.html, text-shrink-invalid.html, and text-shrink-computed.html tests are merged into text-grow-*.html.
We're going to rename tests in this directory later.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |