- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 19:06:49 +0000
- To: public-css-archive@w3.org
As far as I can tell, the reason I removed the explicit "min()/max() is dropped if it has only one child" is that I figured it was covered by the *generic* "replace a node with its result if you can", and just didn't realize that the restrictions I placed on that clause ("in the canonical unit") would be too restrictive.
Anyway, restored now; as part of the special min/max "partial simplification" it'll replace itself with its sole child *regardless* of whether the child is fully resolveable yet.
--
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9559#issuecomment-1823336528 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 19:06:51 UTC