You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mouse over the graph and observe that the hover position does not correspond to the x value logged in the console (and not just as a result of rounding). The console value is from the plotly_hover event and seems to more faithfully represent the actual mouse position.
In contrast, switching to a bar trace seems to align the hovers with the plotly_hover values.
The text was updated successfully, but these errors were encountered:
Although haven't found that documented, my understanding was that data.xvals refer to cursor position while data.points to the corresponding trace's points. See the updated pen
@fhurta is correct here - data.xvals is the cursor position (on whatever x axes exist on this subplot) whereas data.points shows the point(s) we found in data traces to hover on. I don't think there's a bug here.
Example: http://codepen.io/anon/pen/WGvjGX?editors=1111
Mouse over the graph and observe that the hover position does not correspond to the x value logged in the console (and not just as a result of rounding). The console value is from the
plotly_hover
event and seems to more faithfully represent the actual mouse position.In contrast, switching to a bar trace seems to align the hovers with the
plotly_hover
values.The text was updated successfully, but these errors were encountered: