- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Jul 2023 19:22:20 +0000
- To: public-css-archive@w3.org
> So, while we should not change just for the sake of changing, if there are good reasons to change, my understanding is that Chrome has indicated that this is a risk they were willing to take when shipping early. Yes, but there is already [quite a bit](https://chromestatus.com/metrics/css/timeline/popularity/746) of usage in Chromium-based browsers. Making these sites migrate to a new syntax is possible but would need a good enough reason. I can see why it would make sense to change around `text-wrap` along the lines of what was proposed in this issue, but I don't think it's important enough to cause churn and pain for those developers. To me it seems like a good thing we could have done, but not that big of a deal to leave it as-is and move on. For this reason I'm opposed to changing the feature's syntax for the already-shipped values. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9102#issuecomment-1658998792 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 July 2023 19:22:22 UTC