- From: Koji Ishii via GitHub <noreply@w3.org>
- Date: Sat, 05 Jul 2025 13:13:11 +0000
- To: public-css-archive@w3.org
@sakupi01 > This makes me think that the default should match what most users actually prefer - but that's exactly what we're struggling to figure out. > ...shipping with `no-autospace` seems sensible to me, also with web-compat and performance issues. Agreed. Compared to [`text-spacing-trim`](https://drafts.csswg.org/css-text-4/#text-spacing-trim-property), `text-autospace` is: * **Authors' Preference** is a lot more controversial. * **Web-compat** is similarly impacted, but when preferences are a lot more controversial, forcing on is likely to cause more complaints. * **Performance** is a lot more impacted. It's more difficult, or impossible, to optimize for non-CJK scripts due to the nature of the feature. I don't have data if authors wanting no-autospace is more than authors wanting autospace or vice versa, but given these situation, the exact ratio doesn't matter. It's controversial enough to worry about risks. Before, I assumed that it's a lot less controversial, and it has less web-compat impacts. Thanks again @sakupi01 and @frivoal for providing data to correct me. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3038911690 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 5 July 2025 13:13:11 UTC