-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Rangeslider style on select fix #4022
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
Conversation
- which is a more centralised DRY place - use nodeRangePlot3 for range-plot trace, that way we don't override node3 when plotting a trace in a range-plot
- to improve selection perf.
... for modules that define a _module.styleOnSelect method
- as they're only meant to be used on select!
... during selection mousemove. To do so, - make _module.styleOnSelect handle a 3rd argument (in practice, a d3 selection of <g.trace> of the main plot OR the range plot) - similarly for _module.style methods that get called during selections - N.B. has to "fix" one (wrong) finance select assertion
Pinging @mbkupfer who seems to be very good at noticing rangeslider/selection bugs Could you try https://codepen.io/etpinard/pen/KjxWzZ - if you get the chance? Thanks very much! |
Looking good to my eyes. |
Yeah, that would be nice. |
Excellent. I tried to test out many different scenarios including click events and multiple series and didn't see any sync problems. |
@plotly/plotly_js - tweaking a few things in selection / rangeslider land.
fixes #3957
before: https://codepen.io/mbkupfer/pen/zVGwoZ
after: https://codepen.io/etpinard/pen/KjxWzZ (try selecting the bars)