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
When I have a point with a y value that is undefined (representing a data gap) and I hover over it without first hovering over other points (e.g. moving mouse in from under x axis to this point), the glyph and tooltip do this:
The text was updated successfully, but these errors were encountered:
Hey @mira-t 👋 thanks for checking out visx. Can you explain more what you would expect to happen in this case? From a UX perspective it seems like the following would probably be most ideal:
if x or y is defined, use that position
if x or y is undefined, fallback to wherever the cursor or pointer event occurred
I think as a workaround for now you probably could set snapTooltipToDataY={false} on the Tooltip. That seems to work fine in the demo:
Yes, when the x or y is undefined, I would expect the tooltip to fallback to wherever the cursor/pointer event occurred, but no glyph as there is no data.
I also noticed that the glyph only goes to the bottom of the svg if my mouse approaches the chart from below it. If the mouse was previously close to the points to the left or right of the gap it just uses that y-value instead.
When I have a point with a y value that is undefined (representing a data gap) and I hover over it without first hovering over other points (e.g. moving mouse in from under x axis to this point), the glyph and tooltip do this:
The text was updated successfully, but these errors were encountered: