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
[Bug] Chart affected by other chart options #19880
Comments
Even if the observation is correct, scatter.itemStyle API has no decal, so setting it up does not make sense, no? |
@helgasoft correct it doesn't make much sense having the decal there, however, I've noticed other strange behaviour with multiple charts and this was a mistake that took a long time to isolate, find and reproduce (Especially as it only happens if the scatter chart is rendered first) Do you think a misconfigured option (or any option for that matter) should change the behaviour of another chart? What do you think about the behaviour of this example? |
Of course not. And you are right, it is a bug 😓
And yes, scatter series is counted despite not being able to use decals. |
In the second example it sets one decal for the series that should be repeated, as it's within the array as mentioned in the docs you linked. See example of same decal repeated for each series. So I think the example I had in the gist or even a toggle pattern example is a correct example. I want decals to toggle for all series. The above fix is not a repeating pattern of decals. But I think we are starting to move away from the main issue: A charts options (and perhaps rendering order) is affecting another chart |
Version
5.5.0
Link to Minimal Reproduction
https://gist.github.com/brandonstubbs/d1fe4a7d55495a59c3b7d86929f2085b
Steps to Reproduce
The gist is a full reproduction of the issue.
Current Behavior
The decal on the area chart is not on the correct series:
Expected Behavior
If you comment out the decal or you change the order that you set the options on the charts the decal will be correct:
Environment
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: