Fix hover on orphan node

[Tav0]

fix #51

[micahstubbs]

thanks for the contribution @Tav0! will take a look at this

[micahstubbs]

@Tav0, so I tested this new example data on master (without the fix) and I am not able to reproduce the bug. can you tell me more about when you see the bug (see hover broken)?

Could you perhaps add another example to the PR that will show the bug if the fix is not present?

[micahstubbs]

some more details on what I tried in this issue #51

[Tav0]

Hi @micahstubbs sorry for the delay, here it is a gif of the issue. (master branch)

[micahstubbs]

nice, thanks for adding the example! I'll take a look at this, hopefully sometime this week.

[micahstubbs]

hi @Tav0, so checked out your branch

git checkout -b Tav0-fix/hover-orphan-node master
git pull https://github.com/Tav0/visjs-network.git fix/hover-orphan-node

and saw this:

1. the popup appears on the orphan node 6 added to the example (this works on master too)
2. the popup appears on the connected node 5 (this works on master too)
3. the popup does not appear on the newly added new node (this is broken on master too)

[micahstubbs]

@Tav0 could you take another look, and see if you can produce an example where 3) works too?

[micahstubbs]

it looks to me like when we mouse over the new node, the hidePopup event is fired too soon. It fires before we mouse out from the new node.

[micahstubbs]

contrast this with the behavior of Node 6, where the hidePopup event is not fired until we mouse out. This is the expected behavior. this and all previous examples are taken from a local server running the code in this PR.

[micahstubbs]

@Tav0 let's keep at this - I think we are close to a solution here 😄 📈

[micahstubbs]

will close this PR, since I was not able to reproduce the fix.

@Tav0 please do re-open this PR if you would like to help us verify the fix 😄