- From: Ian Kilpatrick via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Oct 2024 21:46:50 +0000
- To: public-css-archive@w3.org
> I'm not convinced we should treat it like a percentage. For example, with a min/max-content of 100px, `fit-content` is basically `clamp(100px, stretch, 100px)` This isn't correct - we recently did a change to follow Firefox in this regard. See: https://github.com/w3c/csswg-drafts/issues/10721 When the stretch is indefinite - `min-size: fit-content` resolves to `min-size: min-content`, and `max-size: fit-content` to `max-size: max-content` respectively. > And doing this like Blink seems more annoying to implement in Servo. I'm curious why this is difficult in Servo? This might result in difficulty when attempting to implement calc-size() for example. I'm pretty convinced that we should just be consistent with 100% here, (again see the `max-height:stretch` example above, it'd be super weird if we coerce an explicitly extrinsic constraint to be intrinsic). -- GitHub Notification of comment by bfgeek Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11006#issuecomment-2403488815 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 October 2024 21:46:50 UTC