- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Aug 2024 20:34:02 +0000
- To: public-css-archive@w3.org
(I discussed this with Ian in person.) Yeah, the Firefox behavior isn't in the spec; Chrome is more correct in ignoring the unresolvable size under the min/max size constraint. But I think Firefox's behavior makes more sense. It's not *perfect*, but it seems *closer* to what the author would expect. I think it's safe too, in that it produces a min size that's smaller (or equal) to what the eventual "real" size is, and a max size that's larger (or equal), so you won't run into situations where the min size is *larger* than the eventual size or vice versa. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10721#issuecomment-2278715071 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 August 2024 20:34:03 UTC