- From: Koji Ishii via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Oct 2023 08:07:54 +0000
- To: public-css-archive@w3.org
@frivoal > Is it because not trimming at all gives results that are more consistent than space-first, even if they're not great? Yes, it's acceptable, though not great. It doesn't change the visual of line-start from without the feature implemented, so no improvements on line-start, but it doesn't regress. In these examples screenshot of `space-first` ([1](https://lists.w3.org/Archives/Public/public-i18n-japanese/2023OctDec/att-0167/02-image.png), [2](https://lists.w3.org/Archives/Public/public-i18n-japanese/2023OctDec/att-0216/image.png)), a) trimming both open parenthesis at line 1 and line 2 is ideal, b) not triming both is acceptable, and c) trimming only one of them is quite bad, especially for headlines. > Maybe we do need a new value, but I wonder how much of this problem we can address using UA stylesheets, for example by setting text-spacing: trim-auto on h1, h2… and maybe also on dt, dd, li… even if the initial value remains space-first? Good idea. This is not easy though, as the problem is about web-compat of existing sites, and they use `<div>` quite often. * If we were to make `trim-auto` as the default, [Aozorabunko](https://www.aozora.gr.jp/cards/000148/files/789_14547.html) for example uses `<div>` and `<br>`. * If we were to make `space-first` as the default, [MSN Japan](https://www.msn.com/ja-jp), [Google News Japan](https://news.google.com/home?hl=ja&gl=JP&ceid=JP:ja) for examples use `<div>`. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9511#issuecomment-1774645988 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 October 2023 08:07:56 UTC