Skip to content

Prevent NaN lonShift from crashing hover#7722

Open
platinops wants to merge 1 commit intoplotly:masterfrom
platinops:scattermap-hover-lonshift-nan
Open

Prevent NaN lonShift from crashing hover#7722
platinops wants to merge 1 commit intoplotly:masterfrom
platinops:scattermap-hover-lonshift-nan

Conversation

@platinops
Copy link
Copy Markdown

@platinops platinops commented Feb 24, 2026

Prevent NaN lonShift from crashing hover on maps when xval is undefined.
Fixes #7702.
I created this since I saw PR #7709 was abandoned/deleted by its author.

@camdecoster
Copy link
Copy Markdown
Contributor

Thanks for the PR. We'll take a look at follow up.

@camdecoster
Copy link
Copy Markdown
Contributor

I think that just catching NaN values is a band-aid fix. I looked into why the values are NaN to begin with, and it has to do with the fact that xval and yval aren't getting set when Plotly.Fx.hover is called with pointNumber in the payload. Could you see if there's a way to set xval and yval to the proper value? Additionally, there might be other places where these values need to be set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: Plotly.Fx.hover error when used on Plotly map

3 participants