- From: Shinyu Murakami via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Feb 2024 10:39:34 +0000
- To: public-css-archive@w3.org
> The intention of `auto` was to align with the platform conventions, whatever they are. So I don't think we can dictate what that is. As far as I know, Apple's platforms (macOS, iOS) have such conventions, but Windows and Linux do not. I understand that Apple's WebKit needs the `auto` value to align with their platform conventions, which are nearly the same as `text-spacing-trim: trim-auto` and `text-autospace: ideograph-alpha ideograph-numeric`, it's OK. But what behavior should be expected on other platforms? I am concerned about a situation that the `auto` value only works well on WebKit, and other UAs do not support it or treat it as same as `normal`. > Is there a reason not to use either `normal` or an explicit keyword? The `text-spacing-trim`'s initial value `normal` is a suboptimal value that is a compromise to avoid negative impact on existing content. I want to recommend to use better settings in most cases. The `trim-auto` value will be good, but if `auto` may have higher quality settings, it may be a better choice. -- GitHub Notification of comment by MurakamiShinyu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9857#issuecomment-1929233081 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 February 2024 10:39:37 UTC