Re: [csswg-drafts] [css-values-4] How to interpolate <ratio>? (#4953)

The CSS Working Group just discussed `[css-values-4] How to interpolate <ratio>?`, and agreed to the following:

* `RESOLVED: Interpolate ratios using log`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-values-4] How to interpolate &lt;ratio>?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4953<br>
&lt;dael> TabAtkins: Currently the value and units spec defines that ratios are interp by devide and interpolate the number. Bad. It's simple but has bad properties. Grossly asymmetrical between tall and wide. tall has 1-0 range and wide is 1-infinity<br>
&lt;dael> TabAtkins: If going from 1-1 to 10-1 if it goes tall it spends most of it's time being close to square. Takes a long time to go 1 -> .1 But if you're going wide you're spending most of the time close to 10<br>
&lt;dael> TabAtkins: A much better way to preserve the symmetry is to take the log of the division results and interpolate that and exponent to get back to the ratio. Gives you idential behavior. Makes sure if you're going 2-1 that halfway is suqare<br>
&lt;dael> TabAtkins: Suggestion for dbaron has other asymmetries. If you want details it's in the issue and oriol has examples of where the assymetry comes in<br>
&lt;fantasai> oriol made demos at http://software.hixie.ch/utilities/js/live-dom-viewer/saved/8634<br>
&lt;dael> TabAtkins: Would like to transition ratios using log of result. I think this is fine for future uses. Produces pleasing visual transition. Symmetry should be good for all cases<br>
&lt;florian> sounds good to me<br>
&lt;dael> TabAtkins: Prep to resolve to use the log. Other thoughts we can go back to the issue<br>
&lt;dael> astearns: Additional comments?<br>
&lt;dael> astearns: Prop: Interpolate ratios using log<br>
&lt;dael> RESOLVED: Interpolate ratios using log<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4953#issuecomment-722054926 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 5 November 2020 00:47:01 UTC