W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [css-values-4] min/max(%, %) should explicitly evaluate against the % value, not the resolved value (#4227)

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jan 2021 17:50:40 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-768460599-1611769839-sysbot+gh@w3.org>
It looks like 

> 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%`

It looks like this is what happens in Chrome as well (the `min` expression is resolved as 100% here).
In comparison, in Firefox it seems to be resolved as 0% (at least, the rendering stays the same if I replace the min() expression with 0%.

Am I correct in understanding that we've resolved on the behavior that Firefox happens to already have here? (and Chrome/Safari's implementations need to be adjusted so that the jsfiddle resolves the min expression to 0% rather than 100%?)

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 January 2021 17:50:43 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:25 UTC