Scaling doesn't take ticks min/max into account

[klausenbusk]

Expected Behavior

When the dataset is "filtered" by using min/max, the scaling of the y-axes should use the "filtered" dataset.

Current Behavior

The scaling is calculated from the full dataset and not the "filtered" dataset.

Possible Solution

Use the "filtered" dataset when calculating scaling?

Steps to Reproduce

https://jsfiddle.net/0426Lvsb/ (click magic and notice that the y-axis scale doesn't change)

Context

I'm using Chart.js to show download stats for Flathub and you can choose a interval (infinity, 365 days, 30 days, 14 days). Some of the data contains some high spikes, which means when you choose 14 days the scaling doesn't match the shown data (most of the chart is empty).

Link: https://klausenbusk.github.io/flathub-stats/

Environment

Chart.js version: 2.9.3
Browser: Firefox Nightly
Project: https://github.com/klausenbusk/flathub-stats/ (deployed here)

[benmccann]

I believe this works the way you'd like it to with 3.0.0-alpha. Can you give it a try?

[klausenbusk]

I believe this works the way you'd like it to with 3.0.0-alpha. Can you give it a try?

I just tried and it does: https://jsfiddle.net/b72kfd9e/14 I assume we can close this issue?

[leeoniya]

@benmccann didn't you guys default lineTension to 0 as part of #7386?

clicking "magic" in this fiddle produces an "interesting" curve ;)

[etimberg]

@leeoniya we did, but I believe that was after the first alpha release. I think we're quite close to a 2nd alpha (#7435 is the big thing we're trying to get in)

[benmccann]

I'm closing this since it sounds like it's addressed. Let me know if there's still something that needs to be looked at