Replies: 1 comment 1 reply
-
Did you mean to reference the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the response. I actually came across the bug in the meantime and just forgot to update my question. First I tried to fix the issue by downgrading r3f which led to different issues with the click handlers. Basically the click would just trigger on the underlying canvas and I could not stop it via I then took a closer look at the markup generated by r3f, which looks somehow like this: <!-- DOES NOT WORK -->
<div> <!-- rf3 container -->
<canvas /> <!-- threejs canvas -->
<div /> <!-- tooltip -->
</div>In the end I was only able to work around it by passing a custom portal ref to <!-- WORKS -->
<div> <!-- rf3 container -->
<canvas /> <!-- threejs canvas -->
</div>
<div>
<div /> <!-- tooltip -->
</div> |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My first time touching threeJS so bear with me :)
I am rendering a bunch of square objects in a 2d plane via react-three-fiber.
Each has a click handler that opens a tooltip react component wrapped with
<Html />coming from react-three/drei.Now when I click on the tooltip a click event gets dispatched on the canvas. The offset to canvas equals the offset to the tooltip that was clicked.
Hopefully someone can point me in the right direction. Otherwise I will try tor reproduce this in a code sandbox.
Beta Was this translation helpful? Give feedback.
All reactions