Hoverability does not follow the spec

[hybridherbst]

Here's a test file:
Hover.glb.zip

Currently, hovering over it and moving the mouse on the object causes all kinds of glitches because it seems that the hover event is repeatedly called when the hovered object changes. That does not match the spec language which mentions hovering should behave similar to how it does in HTML – only leaving the entire subtree of a node would cause hoverUp to be invoked.

[mattmacf98]

the node hierarchy a root starting from 2 which contains children 3-14 and a root at 15 which has the rest as children. I have logged out the old hover node index and new one in the pointer listener and have also logged out the actual hover in and out events.

here is an example

BabylonDecorator.ts:86 OLD HOVERED NODE -1, NEW 13
OnHoverIn.ts:36 EXECUTING HOVER IN FOR 2 BECAUSE OF 13
8BabylonDecorator.ts:86 OLD HOVERED NODE 13, NEW 13
BabylonDecorator.ts:86 OLD HOVERED NODE 13, NEW 26
OnHoverOut.ts:36 EXECUTING HOVER OUT FOR 2 BECAUSE OF 13
2BabylonDecorator.ts:86 OLD HOVERED NODE 26, NEW 26
BabylonDecorator.ts:86 OLD HOVERED NODE 26, NEW 13
OnHoverIn.ts:36 EXECUTING HOVER IN FOR 2 BECAUSE OF 13
4BabylonDecorator.ts:86 OLD HOVERED NODE 13, NEW 13
BabylonDecorator.ts:86 OLD HOVERED NODE 13, NEW 26
OnHoverOut.ts:36 EXECUTING HOVER OUT FOR 2 BECAUSE OF 13
11BabylonDecorator.ts:86 OLD HOVERED NODE 26, NEW 26
BabylonDecorator.ts:86 OLD HOVERED NODE 26, NEW 13
OnHoverIn.ts:36 EXECUTING HOVER IN FOR 2 BECAUSE OF 13

it seems the pointer detects that it is hovering over one of the nodes from that second root which starts at 15 and that is why hover out gets triggered

when I opened this in blender, I saw you had essentially a copy of the geo in the clickToOpen (states)

I think the duplicate meshes under different parent nodes is causing the flickering, could you try either

1. parenting both of these hierarchies under a top level node and adding the hover on that or
2. removing this duplicate state transform heirarchy