The current screen touch input is designed that the input event is fired if the pointer (right controller) is close enough to the tablet (left controller) for the case where VR browser supports WebExtensions API in the future and enables testing AR on VR.
But it's a bit annoying to desktop users because input event can be fired even if user didn't intend to fire, for example user just wants to rotate the tablet but it hits to the pointer.
In the current UI dekstop user can control the pointer right on the tablet screen by pressing and dragging mouse right button on the tablet screen in AR virtual room as if touching the tablet screen. So disabling screen touch input while mouse right button is not being pressed on the tablet screen so far. It improves the user experience.
The current screen touch input is designed that the input event is fired if the pointer (right controller) is close enough to the tablet (left controller) for the case where VR browser supports WebExtensions API in the future and enables testing AR on VR.
But it's a bit annoying to desktop users because input event can be fired even if user didn't intend to fire, for example user just wants to rotate the tablet but it hits to the pointer.
In the current UI dekstop user can control the pointer right on the tablet screen by pressing and dragging mouse right button on the tablet screen in AR virtual room as if touching the tablet screen. So disabling screen touch input while mouse right button is not being pressed on the tablet screen so far. It improves the user experience.