- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Aug 2023 21:20:16 +0000
- To: public-css-archive@w3.org
> 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. With my css author hat on. The reason we quickly adopted `text-wrap: balance;` was that is an obvious improvement almost everywhere and it causes no issues in older browsers. You just add it and things look better in latest Chrome but they were never broken elsewhere. We even added it in a bunch of places before Chrome shipped it in stable because it was so harmless. I wouldn't mind having to do a find/replace if this was taken out of `text-wrap`. > churn and pain for those developers In this specific case I don't think it will cause that. Nothing will break. ----- As a maintainer of `postcss-preset-env` and `stylelint` I wouldn't mind making the tools to help other migrate. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9102#issuecomment-1682996477 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 August 2023 21:20:18 UTC