-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
dropShadow in a multi-series chart applies dropShadow to other series after hovering #4167
Closed
ericlighthofmann opened this issue
Dec 21, 2023
· 0 comments
· Fixed by younginnovations/iatipublisher#1494 or sgkens/velvetvoid#11 · May be fixed by Sheitak/weather-graphics-monitoring#643, Suivie-Physique/suivi-physique#22 or Sheitak/weather-graphics-monitoring#646
Closed
dropShadow in a multi-series chart applies dropShadow to other series after hovering #4167
ericlighthofmann opened this issue
Dec 21, 2023
· 0 comments
· Fixed by younginnovations/iatipublisher#1494 or sgkens/velvetvoid#11 · May be fixed by Sheitak/weather-graphics-monitoring#643, Suivie-Physique/suivi-physique#22 or Sheitak/weather-graphics-monitoring#646
Comments
This was referenced May 20, 2024
This was referenced May 26, 2024
This was referenced Jun 2, 2024
This was referenced Sep 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I have a chart with two series, a bar series and a line series. I've applied dropShadow to the line series here:
dropShadow: { enabled: true, enabledOnSeries: [1], top: 5, left: 5, blur: 5, opacity: 0.2 }
After hovering over a point in the bar series to view the tooltip, the dropShadow is applied to my bar and persists until the chart is re-rendered. See the screenshot, I hovered over the first two points but did not hover over the third:
Steps to Reproduce
Reproduction Link
Here is a minimal example - hover over a bar in the series to see the dropShadow be applied to the bar:
https://codepen.io/Eric-Hofmann/pen/MWxWeYZ
Edit:
Removing the hover state solves it, but is still probably a bug:
states: { hover: { filter: { type: 'none', } }, }
The text was updated successfully, but these errors were encountered: