Skip to content
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

Spiderweb Shared Tooltip not rendering #17472

Closed
rw-jchartis opened this issue Jul 6, 2022 · 10 comments · Fixed by #17485
Closed

Spiderweb Shared Tooltip not rendering #17472

rw-jchartis opened this issue Jul 6, 2022 · 10 comments · Fixed by #17485

Comments

@rw-jchartis
Copy link

Expected behaviour

Shared Tooltip should render multiple datapoints for the respective variable.

Actual behaviour

Tooltip does not render at all and the following error is thrown in the console.

highcharts_spiderweb

Live demo with steps to reproduce

Shared tool tip is no longer working on the demo provided via the Highcharts website. Just hover over a datapoint and you will see the tool tip does not render.
https://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/highcharts/demo/polar-spider

Product version

Latest version from https://code.highcharts.com

Affected browser(s)

Chrome, Firefox, IE.

@pawellysy
Copy link
Contributor

Thanks @rw-jchartis for reporting this issue!
It's a regression, which popped up in the latest version v10.2.0.

internal note
Bisected to 14d5a98

FYI @bre1470

@raf18seb
Copy link
Contributor

raf18seb commented Jul 8, 2022

The problem is with a this context which should be a polar composition instead of series.
Possible culprit:

searchPoint: (
PolarSeriesComposition['kdByAngle'] extends true ?
PolarAdditions['searchPointByAngle'] :
Series['searchPoint']
);

Workaround (pass a correct context): https://jsfiddle.net/BlackLabel/x64hetLn/

point = s.searchPoint.call(s.polar, e, compareX)

@GabrieleT0
Copy link

Same problem here. Sorry for the duplicate. Is there a way to fix this problem temporarily?

@pawellysy
Copy link
Contributor

Hi @GabrieleT0, The workaround is posted in the previous post: https://jsfiddle.net/BlackLabel/x64hetLn/

@GabrieleT0
Copy link

Hi @GabrieleT0, The workaround is posted in the previous post: https://jsfiddle.net/BlackLabel/x64hetLn/

Thank you so much.

@jsokol
Copy link

jsokol commented Jul 19, 2022

Any idea when this bug fix will go live? We would prefer not to implement the aforementioned workaround if this will be updated sooner, rather than later. Thanks.

@pawellysy
Copy link
Contributor

Hi @jsokol, We are currently during the vacation period, so all of the fixes/releases are currently on hold. For now, you need to use the workaround. Sorry for the inconvenience :(

@jsokol
Copy link

jsokol commented Jul 20, 2022

Hi @jsokol, We are currently during the vacation period, so all of the fixes/releases are currently on hold. For now, you need to use the workaround. Sorry for the inconvenience :(

Totally understand you guys being on vacation and I'm not pushing for an immediate fix. I guess what I'm trying to figure out is when you'll be off vacation and fixes/releases are no longer on hold so this can be addressed? Are we talking days?
Weeks? Months? What kind of priority will this be given when you are back? Thanks.

@pawellysy
Copy link
Contributor

@jsokol, the fix is already in review, so in terms of development, there is not much to take into consideration. It is a matter of the date of the next release, which I would expect to be near the end of August.

@jsokol
Copy link

jsokol commented Jul 21, 2022

@jsokol, the fix is already in review, so in terms of development, there is not much to take into consideration. It is a matter of the date of the next release, which I would expect to be near the end of August.

This helps a ton! Thank you!

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

Successfully merging a pull request may close this issue.

6 participants