- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jun 2024 15:28:58 +0000
- To: public-css-archive@w3.org
Overall, the Chrome team's consensus position is that shorthandifying well-established properties after the fact is risky, has significant implementation and developer-churn/confusion cost, and generally doesn't provide enough developer benefit to justify this risk, churn and cost. So we're opposed to doing that generally. Therefore, I suggest we resolve the issue (8398) with this design guidance: "don't shorthandify well-established CSS properties". (Aside: in addition, Tab commented [here](https://github.com/w3c/csswg-drafts/issues/10321#issuecomment-2190024736) about additional reasons beyond the above why we should't shorthandify `position` for anchor positioning. However, his arguments have some relationship to my points above, since they are an example of how shorthands can be more confusing than the alternative.) -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8398#issuecomment-2191998628 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 June 2024 15:28:59 UTC