# Strange controller's behaviour in Oculus browser

**URL:** <https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513>\
**Category:** Questions\
**Tags:** vr, xr, controller\
**Created:** [December 7, 2025, 5:18pm UTC](https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513 "2025-12-07T17:18:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yesbird](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/yesbird/32/46097_2.png) [@yesbird](https://discourse.threejs.org/u/yesbird)\
**Post date:** [December 7, 2025, 5:18pm UTC](https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513/1 "2025-12-07T17:18:35Z")

</div>

Greetings !

While working on my [algebraic surface viewer](https://mathview.yesbird.online/) with XR support, I am stuck on strange behaviour of the controller in Oculus browser.

Steps to reproduce:

1. Open [https://mathview.yesbird.online/](https://mathview.yesbird.online/) in Oculus browser.
2. Select surface, _not_ entering XR mode.
3. Move the cursor outside the rendering canvas (say, point to any icon).

After that the controller will stick to the surface and will not release it - looks like '‘selectend’ event is not firing. Could you please check this issue on your headset, if you have one and suggest the way to solve it ?

I spent three sleepless nights trying to fix it. Unfortunately I can’t even write anything to console, as my Oculus Go doesn’t support it.

---

<div class="post-metadata">

**Author:** ![PavelBoytchev](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/pavelboytchev/32/38639_2.png) [@PavelBoytchev](https://discourse.threejs.org/u/PavelBoytchev)\
**Post date:** [December 7, 2025, 5:46pm UTC](https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513/2 "2025-12-07T17:46:39Z")

</div>

If the `pointerleave` event is fired on the canvas when the pointer leaves it, you can manually dispatch `selectend` or even directly release the controller. This is just an idea, untested, but worth trying.

---

<div class="post-metadata">

**Author:** ![yesbird](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/yesbird/32/46097_2.png) [@yesbird](https://discourse.threejs.org/u/yesbird)\
**Post date:** [December 7, 2025, 5:52pm UTC](https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513/3 "2025-12-07T17:52:28Z")

</div>

Thanks, I will try it !

---

<div class="post-metadata">

**Author:** ![yesbird](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/yesbird/32/46097_2.png) [@yesbird](https://discourse.threejs.org/u/yesbird)\
**Post date:** [December 7, 2025, 7:39pm UTC](https://discourse.threejs.org/t/strange-controllers-behaviour-in-oculus-browser/88513/4 "2025-12-07T19:39:30Z")

</div>

It was a good idea, but unfortunately it’s not woking - I tried ‘pointerout’ also - no success.  
I guess the reason is the browser in Oculus Go implemented very rudimentary and inaccurate, will try to find another workaround …