Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering artifacts when panning an area chart #8699

Closed
iddings opened this issue Mar 22, 2021 · 4 comments · Fixed by #8703
Closed

Rendering artifacts when panning an area chart #8699

iddings opened this issue Mar 22, 2021 · 4 comments · Fixed by #8703

Comments

@iddings
Copy link

iddings commented Mar 22, 2021

Expected Behavior

Area charts should render properly.

Current Behavior

If animations are disabled, and the zoom plugin is loaded, artifacts appear when panning out of the data range.

Initial Load:

Annotation 2021-03-22 180646

After Panning:

Annotation 2021-03-22 180649

Possible Solution

Not a solution, but I believe the issue to be in Chart.js, not the zoom plugin, as I've replicated the issue with my own custom zoom plugin.

Steps to Reproduce

Configure an area chart with a time x-axis (to allow panning past the range of data), and pan the data out of range.

https://jsfiddle.net/ke12g95r/5/

@etimberg
Copy link
Member

This also occurs with just a plain linear X axis. My gut is that the filler plugin is not correctly filtering points that are off the chart area, but it only seems to happen in certain scenarios

@kurkle
Copy link
Member

kurkle commented Mar 22, 2021

To me, looks like it draws to the first hidden point, but fails to go to origin from there, before closing the path. Could be simple fix or not :)

@kurkle
Copy link
Member

kurkle commented Mar 23, 2021

This behavior comes from #7793

@iddings
Copy link
Author

iddings commented Mar 23, 2021

guess it was a simple fix after all. thanks for the quick help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants