Re: [csswg-drafts] [css-text] Reconsider the initial value of the `text-autospace` property (#12386)

The CSS Working Group just discussed ``[css-text] Reconsider the initial value of the `text-autospace` property``, and agreed to the following:

* `RESOLVED: Allow shipping with no-autospace as initial value, continue discussing eventual default behavior`

<details><summary>The full IRC log of that discussion</summary>
&lt;emilio> Rossen: this issue is still under active discussion<br>
&lt;emilio> ... I know this is something the chrome team wanted to bring forward to unblock implementation<br>
&lt;emilio> ... is koji on the call?<br>
&lt;emilio> fantasai: I think we all agree it should be fine to ship initially with default no autospace<br>
&lt;emilio> ... what the default should be ultimately is the debate in the issue<br>
&lt;emilio> ... but we can resolve that no autospace is an acceptable default for the time being<br>
&lt;emilio> florian: That's chrome's position as well<br>
&lt;emilio> Rossen: anything else that you want to point out?<br>
&lt;emilio> fantasai: I think we need to continue the discussion about eventual default<br>
&lt;emilio> q+<br>
&lt;florian> +1<br>
&lt;fantasai> emilio: Does the property definition allow changing defaults easily? Is there 'normal'?<br>
&lt;fantasai> fantasai: yes<br>
&lt;Rossen3> ack emilio<br>
&lt;emilio> emilio: then that sounds fine<br>
&lt;emilio> PROPOSED: Shipping with default autospace off is fine for now, keep discussing eventual default<br>
&lt;fantasai> RESOLVED: Allow shipping with no-autospace as initial value, continue discussing eventual default behavior<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3028532137 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 July 2025 16:40:05 UTC