Re: [csswg-drafts] [css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value (#4227) from Xiaocheng Hu via GitHub on 2019-08-20 (public-css-archive@w3.org from August 2019)

From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Aug 2019 21:29:37 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-523202477-1566336575-sysbot+gh@w3.org>

For reference:
Safari (Version 12.1.2 (14607.3.9)) resolves `min(%, %)` against the resolved value.
See example at http://jsfiddle.net/t9bk6p0q/1/, where `min(0%, 100%)` is resolved as `100%`

I originally raised this issue as I wasn't aware of `background-position`. As I'm implementing `min/max` in Blink, I need to make sure that if we support evaluation of % against negative values, the added code paths are reachable.

Now that it's reachable, it's no longer an issue for me.

-- 
GitHub Notification of comment by xiaochengh
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4227#issuecomment-523202477 using your GitHub account

Received on Tuesday, 20 August 2019 21:29:38 UTC