Hey @acvigue . Thanks for the feature request.

Maybe someone else can help in the meantime, but this sounds like it might fit in well with what I've been working on for v4 or after, depending on what the team thinks.

I'll add this to my personal to-do list, anyway.

To get a better idea of the requirements, would it be possible to post your workaround below? Even a bit of pseudocode would be fine. Or if you pulled it from a Three.js example, a link would be great!

Hi! Thanks. Yeah, I'm using nuxt 3 with native threejs and just use window.createeventlistener("pointermove" / "pointerenter" / "pointerleave") instead of tying the events directly to the canvas element.

Edit: Still using same raycaster logic and all but am just listening to events from the window instead of element if that makes more sense