- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 02 Jul 2025 16:40:04 +0000
- To: public-css-archive@w3.org
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> <emilio> Rossen: this issue is still under active discussion<br> <emilio> ... I know this is something the chrome team wanted to bring forward to unblock implementation<br> <emilio> ... is koji on the call?<br> <emilio> fantasai: I think we all agree it should be fine to ship initially with default no autospace<br> <emilio> ... what the default should be ultimately is the debate in the issue<br> <emilio> ... but we can resolve that no autospace is an acceptable default for the time being<br> <emilio> florian: That's chrome's position as well<br> <emilio> Rossen: anything else that you want to point out?<br> <emilio> fantasai: I think we need to continue the discussion about eventual default<br> <emilio> q+<br> <florian> +1<br> <fantasai> emilio: Does the property definition allow changing defaults easily? Is there 'normal'?<br> <fantasai> fantasai: yes<br> <Rossen3> ack emilio<br> <emilio> emilio: then that sounds fine<br> <emilio> PROPOSED: Shipping with default autospace off is fine for now, keep discussing eventual default<br> <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