lukbukkit / chartist-plugin-tooltip

Tooltip plugin for Chartist.js
MIT License
16 stars 13 forks source link

Not working #2

Closed NaNraptor closed 5 years ago

NaNraptor commented 5 years ago

This JS fiddle doesn't seem to be working:[( https://jsfiddle.net/AlexanderKozhevin/aapycL87/ )]

I tried implementing it too, which didn't work either.

By not working I mean no tooltip get's displayed on hover/click or any other action

lukbukkit commented 5 years ago

I'll look into it, but the resources used on the fiddle are looking outdated. I try to rebuild it

lukbukkit commented 5 years ago

Sorry but I guess I don't have a lot of spare time in the next week. I'll to do this as soon as possible.

lukbukkit commented 5 years ago

I'm currently on vacation and I'm going to look into the issue when I'm home again.

lukbukkit commented 5 years ago

Hey, I've googled a little bit and found this issue chartist-plugin-tooltip#127 about the jsfiddle you've mentioned. It's deals with the same problem as this issue (the fiddle doesn't work).

The user @clottman has created a version which works by updating the libraries and removing unnecessary code. I've took her version and updated the libraries again and it still works: https://jsfiddle.net/g16kv5s2/1/

~And here's the example which (I guess) wants to archive a custom hover effect: https://jsfiddle.net/h8wys0tp/2/. I've had edit the code a little bit, because the data.element.replace(circle); call prevents the tooltip plugin from working.~

lukbukkit commented 5 years ago

Okay I worked a little bit more on the issue and why there are problems when using .replace. Everything relates to this pull request chartist-plugin-tooltip#72. If you are using ct-area or ct-line as a replacement for your data point it'll get ignored by the css rule.

Here's a corrected version of the fiddle, you've linked: https://jsfiddle.net/9gzqnrd8/9/ Thanks again for your attention and I'll update the README.me soon

lukbukkit commented 5 years ago

If something doesn't work as expected please reopen this issue.