- From: Koji Ishii via GitHub <noreply@w3.org>
- Date: Sat, 09 Aug 2025 14:35:14 +0000
- To: public-css-archive@w3.org
@jfkthame Great to hear Gecko is working on this too. > I think wherever reasonably possible, the browser should do "good" rendering by default I'd like to clarify that this is a discussion of what the "good" rendering is. Performance and web-compat were the original reasons to start this discussion, and they're still part of the reasons, but it is now clear that a good number of authors prefer no-autospace because it is "good" rendering. I hope more authors experience the feature on the web, so that the discussion is based on the real web experiences, rather than a hypothesis that "good for printing is good for the web too". I've been dogfooding it for ~1.5 years, default-on and default-off. My dogfooding experiences: * In 98% of cases, I forget whether it's on or off. * There were 2 cases where I wished the autospace, while dogfooding default-off. * There were more cases where the autospace hindered the readability, while dogfooding default-on. Not too many though, like once a week or two, except dates where I always prefer no-autospace. My hypotheses so far is that, in most cases, the web uses smaller `line-height` than printing. Due to less vertical spacing, less spacing in horizontal works better. There are cases where turning it on can improve the typography, so Gecko implementing it is a great news. In my personal opinion, I'd turn it on when the content has taller `line-height` (1.8 or more, common Japanese printing setting), and uses Latin fonts for Latin letters/digits. In other cases, no-autospace looks "good" rendering to me. -- GitHub Notification of comment by kojiishi Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3171181238 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 9 August 2025 14:35:15 UTC