I tried taking a video to demonstrate the issues, but I seem to have hung the headset. I think the Quest probably just can’t do Mozilla Hubs with adequate performance.
It has no trouble at all with similar environments in native apps, so again I wonder if WebVR is to blame.
EDIT: Honestly I wish I could get a video of the truly comedic amount of problems this has caused the headset. First I got a dialog that “Oculus System” had stopped responding, then the dialog separated into two pieces at a jaunty angle to each other and the display froze. Then I tapped the power button, and got a dialog asking if I wanted to power off the headset, but I was unable to click any buttons. One of the controllers seemed to be tracking inverted from reality somehow (pointed along the opposite vector in VR from how the real controller was pointed.) The other one was sort of gently orbiting.
Honestly, I have found VR to be a pretty buggy experience overall, but this is definitely the worst behavior I have ever seen from this platform. It’s pretty funny.
I have personally found VR mozilla hubs worse than computer screen mozilla-hubs.