- From: Florian Rivoal via GitHub <noreply@w3.org>
- Date: Mon, 29 Sep 2025 02:54:15 +0000
- To: public-css-archive@w3.org
`text-autospace` is indeed designed to replace the need to put this kind of spacing in markup, and its `replace` value enables it to deal with documents that have that kind of markup anyway. So I think the basic need is addressed. > Therefore, documents abusing an ASCII space will not migrate to `text-autospace` because the width by `text-autospace` it too narrow. This may be true in some cases, but I don't think it is true generally. Maybe documents use the ASCII space not because it has the exact width the author want, but because the author wants *some* spacing. The CSS-WG and the i18n WG have determined 1/8th of an ideograph is a good compromise. It won't make everyone happy in all situations, but it should be good often enough. > `text-autospace` should allow adjustment of the width. The intent here is to avoid over-complicating things initially. There may be a need to control the size of the space. There may be a need to control the size of the space differently in different contexts… By first introducing the on/off switch, have it broadly deployed, and after a while, checking what the remaining common requests are, we have a better chance of solving what people actually need, instead of setting up something for what we guess people might need, and risk make it too complicated, or complicated in the wrong way. Given that `text-autospace` has not yet fully been rolled out, I would prefer to wait before we add more options. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12868#issuecomment-3344675157 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 29 September 2025 02:54:16 UTC