Chromium

fantasai@ updated the specification and both values of text-edge are required [0]. so the single value of "cap" seems invalid, and chrome converts it into "auto"

[1] text-box: normal | <'text-box-trim'> || <'text-box-edge'>  
[2] text-box-edge: 	auto | <text-edge>                         
[3] <text-edge> = [ text | ideographic | ideographic-ink ]
              | [ text | ideographic | ideographic-ink | cap | ex ]
                [ text | ideographic | ideographic-ink | alphabetic ]

[0] https://github.com/w3c/csswg-drafts/issues/10703

[1] https://drafts.csswg.org/css-inline-3/#propdef-text-box

[2] https://drafts.csswg.org/css-inline-3/#propdef-text-box-edge

[3] https://drafts.csswg.org/css-inline-3/#typedef-text-edge

As per the comment #2. Commented on https://github.com/WebKit/standards-positions/issues/432#issuecomment-2556497147 too.

Thank you Koji and Lingqi for looking into this.

I meant to say that we intendedly take the initial value of text-box-edge, which is "auto", when parsing an invalid text-box-edge value.

The current behavior is working as intended (based on our current understanding of specification), but understandably that it might confuse someone. To discuss what the expected result should be, maybe it would be better to raise a specification issue.

Comment #6:

I believe the comment 2 means that text-box: trim-start cap is an invalid value, and should not compute to text-box: trim-start auto.

Thanks, that's a good point. Making it invalid, and thus inherits from parent, produces the same result as "computes to auto" for the test, so I think Blink is correct result-wise, but you're right that they are different. Let me check with the style expert.

Project: chromium/src
Branch: main
Author: Koji Ishii <kojii@chromium.org>
Link:      https://chromium-review.googlesource.com/6151521

[text-box-trim] Rewind the stream when ConsumeTextBoxEdge fails

[text-box-trim] Rewind the stream when `ConsumeTextBoxEdge` fails 
 
This patch fixes `ConsumeTextBoxEdge` to rewind the input 
stream if the parsing fails in the middle of the consumption. 
 
Bug: 385160696 
Change-Id: Ib8ffbf6ab9731dd4443536ef13abefe5c354b63c 
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6151521 
Reviewed-by: Kent Tamura <tkent@chromium.org> 
Auto-Submit: Koji Ishii <kojii@chromium.org> 
Commit-Queue: Kent Tamura <tkent@chromium.org> 
Cr-Commit-Position: refs/heads/main@{#1403286}