- From: Fuqiao Xue via GitHub <noreply@w3.org>
- Date: Thu, 03 Jul 2025 07:51:24 +0000
- To: public-css-archive@w3.org
Link to previous discussion: https://github.com/w3c/csswg-drafts/issues/6950 ----- > Whether "on by default" or "off by default" doesn't make any differences in the majority of cases, because most existing pages have an ASCII space to where the text-autospace would insert the space, part because it's the tradition since 1980, part because the majority of style guides require to do so. Does Google have data to support this conclusion? My personal experience is exactly the opposite. ----- > For example, a style guide from JETF removed the space in their version 3.0, published in 2019. Did they publish a specific reason? I have discussed this issue with different people (for example, in https://github.com/w3c/clreq/issues/14 ). The reason many people do not add spaces is not because they do not think there is a need for the extra spacing between Chinese/Japanese and Western text, but because they think U+0020 pollutes the source code, because style and content should be separated. Many people think that this spacing is style, not content. In addition, it is easy to make mistakes when adding spaces manually, for example, some people add spaces before full-width punctuation marks. -- GitHub Notification of comment by xfq Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3031252405 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 July 2025 07:51:24 UTC