You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Chrome 35 and Chromium 35, consistently, after a hundred or so (varies) mouseover/mouseout combos, intersects seems to come back negative when it should not.
In Chrome 35 and Chromium 35, consistently, after a hundred or so (varies) mouseover/mouseout combos, intersects seems to come back negative when it should not.
It's inside this conditional - https://github.com/jeromeetienne/threex.domevents/blob/master/threex.domevents.js#L268
If I put a console.log inside this conditional, after this bug manifests, that console.log line is never reached.
However if I set an inspector breakpoint at the line with the console.log, the breakpoint trips with the next event.
The bug manifests with developer tools open or closed, with Three.js r59 and r67.
Meanwhile I cannot replicate the bug in Iceweasel 24.6.0.
The text was updated successfully, but these errors were encountered: