As described in the Web API docs, a click event "fires after both the mousedown and mouseup events have fired, in that order."
The current useClick hook uses the OnPickTrigger, which is fired "when the user touches/clicks on a mesh.". This appears to be roughly equivalent to running after the mousedown event, but before the mouseup event.
I propose modifying the useClick hook to use the OnPickUpTrigger instead, as this seems to more closely align with standard click behavior.
As described in the Web API docs, a click event "fires after both the mousedown and mouseup events have fired, in that order."
The current useClick hook uses the OnPickTrigger, which is fired "when the user touches/clicks on a mesh.". This appears to be roughly equivalent to running after the mousedown event, but before the mouseup event.
I propose modifying the useClick hook to use the
OnPickUpTrigger
instead, as this seems to more closely align with standard click behavior.