Re: [csswg-drafts] [css-text][text-spacing] Visual regressions of line-start at portals and news sites (#9511)

The CSS Working Group just discussed `[css-text][text-spacing] Visual regressions of line-start at portals and news sites`, and agreed to the following:

* `RESOLVED: Accept Murakami's proposal to simplify to text-spacing: normal | trim-start | space-first | trim-auto | space-all | trim-all | auto`
* `RESOLVED: remap property value space for text-spacing`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Zakim, open queue<br>
&lt;Zakim> ok, Rossen_, the speaker queue is open<br>
&lt;frances__> chris harrelson: css property is text-spacing trim<br>
&lt;fantasai> spec -> https://www.w3.org/TR/css-text-4/#text-spacing-trim-property<br>
&lt;frances__> christ: current spec causes compatibility issues in japanese sites<br>
&lt;florian> q+<br>
&lt;frances__> chris h: existing behavior has use cases, make the default what is currently case, add keywords, current comment is out of date, add normal<br>
&lt;frances__> chris h: second discussion for additional keywords to add, propose to segment, discuss, and resolve<br>
&lt;Rossen_> ack florian<br>
&lt;frances__> florian: thinks there's a shortcut, different from written, identical to current behavior and adjacent would be better than current with no combat problems of current draft, and would support<br>
&lt;frances__> florian: keep space in start, and trim adjacent, cohesive investigation<br>
&lt;bradk> Rossen_:  nice. I recognized the bird sounds from when I was in Maui last month. 👍<br>
&lt;frances__> chris h: thank you for clarifying<br>
&lt;fantasai> florian: Current behavior is space-all, we're trying to choose an initial value that's the intersection of what's better and what's Web-compatible<br>
&lt;vitorroriz> q+ (can be by text): so "normal" would be space-all ?<br>
&lt;frances__> rossen: request for other feedback<br>
&lt;emilio> looks sensible to me at a glance<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1853187016<br>
&lt;astearns> q+ vitorroriz<br>
&lt;frances__> fantasai: proposal to add new value normal to represent initial value with space start trim adjacent and allow end, table of what happens at start edge, end edge, and between<br>
&lt;frances__> fantasai: current spec says that we would use space first as start and trim adjacent edge, not web compatible. Proposal to introduce normal keyword, remember initial value and possibly tweak it.<br>
&lt;Rossen_> ack vitorroriz<br>
&lt;frances__> vitor: normal value wouldn't be equivalent to space? fantasai: no<br>
&lt;frances__> fantasai: would be safest option, and possibly improve. from investigation main issues are on the start edges have not come up with problems of trim adjacent behavior at the end<br>
&lt;fantasai> s/space/space-all/<br>
&lt;astearns> s/Rossen_:  nice. I recognized the bird sounds from when I was in Maui last month. 👍//<br>
&lt;frances__> rossen: sibling property of auto-space possibly something equivalent<br>
&lt;astearns> s/Rossen_: is that Hawai’i?//<br>
&lt;frances__> florian: with each issue on GitHub, everyone feels pretty aligned<br>
&lt;fantasai> PROPOSED: Initial value of text-spacing is 'normal' representing the 'space-start trim-adjacent allow-end' behavior<br>
&lt;frances__> rossen: summarize ask for proposed path forward?<br>
&lt;florian> s/with each issue/within issue<br>
&lt;frances__> florian: has the proposed resolution<br>
&lt;frances__> rossen: any additional comments to proposed resolution?<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1862787959<br>
&lt;fantasai> Value syntax would be: normal | trim-start | space-first | trim-auto | space-all | trim-all | auto<br>
&lt;frances__> florian: what do we do with other values? auto is already in spec, would be how to rebalance rest set of values<br>
&lt;fantasai> Current syntax is: space-all | trim-auto | [ allow-end || space-first ] | trim-all | auto<br>
&lt;frances__> florian: removes ability to combine space first with the name of the value at the start end, trim adjacent in the middle, removes trim end variant of space first<br>
&lt;frances__> florian: most were not useful in implementation in browsers<br>
&lt;frances__> rossen: ask for opinions?<br>
&lt;vitorroriz> q+<br>
&lt;frances__> fantasai: supports change<br>
&lt;Rossen_> ack vitorroriz<br>
&lt;frances__> vitor: auto value will be there?<br>
&lt;frances__> fantasai: yes<br>
&lt;frances__> florian: auto matches operating systems native behavior. default would be normal<br>
&lt;frances__> fantasai: proposal to rename auto to match-platform to be more obvious<br>
&lt;frances__> rossen: objections? none, resolved<br>
&lt;fantasai> s/proposal to/we could also/<br>
&lt;fantasai> RESOLVED: Accept Murakami's proposal to simplify to text-spacing: normal | trim-start | space-first | trim-auto | space-all | trim-all | auto<br>
&lt;frances__> RESOLVED: remap property value space for text-spacing<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1864881659 using your GitHub account


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

Received on Wednesday, 20 December 2023 17:41:37 UTC