- From: bryan rasmussen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Sep 2020 08:55:10 +0000
- To: public-css-archive@w3.org
Ok, I guess that's fair enough, although what my thinking was that when https://www.w3.org/TR/css-values-3/#calc-notation says "It can be used wherever <length>, <frequency>, <angle>, <time>, <percentage>, <number>, or <integer> values are allowed." it meant that it would be used at a property - like width - not limiting what it could intake. So my theory was that as max-content can be used at width, and max-content will output a length, then max-content will be usable as an input to min, max, clamp, calc etc. on the width property. >We agree it would be nice to allow calculations with keywords, but it's actually quite difficult because the keywords can map to rather complex behaviors. I haven't done international technical standardization, but I have done international financial standardization (UBL, working for Denmark) so I can certainly recognize that what I would like to see just might not work the way I was hoping! Back to my naive expectation I was hoping that it would be possible to add some statement like Any keyword usable where one of these functions is usable that returns a value usable by these functions can be used in these functions with the following rules - the keyword should be evaluated as if it were being applied directly on the property to determine what its output value should be, thus if for example max-content when used in a width property would return 250px then width: calc(max-content - 25px) would end up being width: 225px. However, if there are various reasons that something simple (perhaps it's simplistic) like that won't do the trick then I guess I will have to be satisfied with the knowledge that you would like to make it work and undoubtedly will some day. Thanks, Bryan Rasmussen -- GitHub Notification of comment by bryanrasmussen Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5554#issuecomment-699875031 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 September 2020 08:55:12 UTC