- From: Tim Nguyen via GitHub <noreply@w3.org>
- Date: Wed, 25 Jun 2025 00:03:55 +0000
- To: public-css-archive@w3.org
> @jensimmons in the future please raise an issue here before shipping a feature that does not match the spec. > I’d like to hear more about the notion that we can change the default in the future. Shipping a feature with a particular default usually tends to constrain us. The impact of changing the default to `normal`, is the same as shipping with the correct default (`normal`) without having shipped the property before in this case, since `no-autospace` is basically no-op compared to what browsers are shipping currently. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12386#issuecomment-3002198241 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 June 2025 00:03:56 UTC