- From: Ashley Kolodziej via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Nov 2022 04:54:19 +0000
- To: public-css-archive@w3.org
This is wild - from an outside perspective, I genuinely thought this was a deprecated property. The thought process that led to that was something like: - Yikes, who stretches type? - Oh, we made all kinds of inadvisable design choices in the 90s. - Ahh, yeah that’s probably it. Must just be a leftover of that era, moving on. Width is more intuitive to me for sure, not just because of the OpenType naming convention, but because it is more consistent with my mental model of how the units for this property work. I’m used to thinking of something having a width of 50%, and having that be half the width of the default state. I’m not used to stretching an item to 50%, because stretching implies that things get longer or wider, not more compressed. I really appreciate this discussion, as well as the concern with technical debt and testing regarding adding an alias. I’ll learn either way, but I thought it was interesting that this conflicted so much with what I was taught to do as a designer that my brain invented an origin story to make it stop. -- GitHub Notification of comment by ashleykolodziej Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/551#issuecomment-1318074343 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 November 2022 04:54:21 UTC