[csswg-drafts] [css-text][text-spacing] Propose to make `allow-end` as the default behavior for the line ennd (#9521)

kojiishi has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-text][text-spacing] Propose to make `allow-end` as the default behavior for the line ennd ==
Currently, the default behavior of line-end for the [`text-spacing-trim`](https://drafts.csswg.org/css-text-4/#text-spacing-trim-property) property is defines as:
> set [fullwidth closing punctuation](https://drafts.csswg.org/css-text-4/#fullwidth-closing-punctuation) with half-width glyphs (flush) at the end of each line

If the author specifies the [`allow-end`](https://drafts.csswg.org/css-text-4/#valdef-text-spacing-trim-allow-end):
> Set [fullwidth closing punctuation](https://drafts.csswg.org/css-text-4/#fullwidth-closing-punctuation) with half-width glyphs (flush) at the end of each line if it does not otherwise fit prior to justification, else set the punctuation with full-width glyphs.

From the dogfood feedback, I'd like to propose to change the default behavior to `allow-end`. We can add a value for the current default behavior if needed.

This proposal is because when you're typing in editable content. The current default behavior trims the last character as you type, making them difficult to distinguish whether it's full-width or half-width, until users type the next character. Some IMEs on desktop platforms remember which was used last time, making this symptom more difficult.

This happens quite frequently for Japanese/Simplified Chinese/Korean, where the comma and full stops (periods) are in the "closing" shape. Not as frequent for Traditional Chinese.

I don't know the motivation and the past discussions to make `allow-end` as the default behavior. If it has big reasons and the WG decided to make a trade-off, could someone please share?

From my current perspective, the feedback looks reasonable to me, and the difference between the current default and `allow-end` looks hardly noticeable, so this looks like a reasonable change. It may be more noticeable when `text-align: right` or `center`. If that was the motivation, I think it's fine to use the current behavior for thoese cases because editing such text isn't very common.

Thoughts? /cc @fantasai @frivoal @nt1m @vitorroriz @Clqsin45 @MurakamiShinyu @himorin @kidayasuo


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9521 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 25 October 2023 11:36:10 UTC