- From: David Leininger via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 19:47:25 +0000
- To: public-css-archive@w3.org
I agree with @ddamato > Ultimately, I think @tabatkins [comment about not addressing all the scenarios](https://github.com/w3c/csswg-drafts/issues/7707#issuecomment-1239842790) is the best path forward. It just means we need to be clear about what this is expected to solve and what it will not. Reading through all of this, I keep thinking the same thing, how would the people I work with use this? I work with a lot of people who would never know how to write the calc function to handle the basic functionality. Most of the time they wouldn't really look for a solution to copy and paste in, they would just try to guess numbers that look "correct" or use what the designer provided. That is a very limited and rigid solution. If there was a value they could add easily to handle most cases, I think they would reach for it a lot. There are properties/values in CSS that only work when the other elements have the correct values as well. I think it's worth addressing the simple use cases with a value that is easy to understand. Then, if the author needed to do something more complex, they would have to write all of the radii independently for the specific use case. -- GitHub Notification of comment by davidleininger Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7707#issuecomment-1756119700 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 19:47:26 UTC