Current Issues in x3dom VR Mode (WebXR branch)

I have been trying the WebXR integration by testing the webxr GitHub branch(pull request: https://github.com/x3dom/x3dom/pull/1235) and found these issues:

No support to navigate to different viewpoints once in VR mode. Webpage freezes once inside VR mode(cannot control viewpoints from HTML buttons, cannot click toggle VR button to return to the original webpage. Demo page: https://metagrid2.sv.vt.edu/~raghavsethi/
The webxr GitHub branch uses “local-floor” as reference space which means “origin is at the floor in a safe position for the user to stand”. However, some use cases require the headset to be at the origin of the x3d scene (e.g., 360 degrees photosphere). I am unsure if x3dom developers can override the XRReferenceSpaceType from the HTML page.
When the user switches to VR mode, the headset is not present at the origin of the scene. This behavior is observed in both “local-floor” and “local” XRReferenceSpaceTypes. I have created the webpage https://metagrid2.sv.vt.edu/~raghavsethi/photoxr-local.html to test the behavior. The webpage has “local” XRReferenceSpaceType in the x3dom custom script. This webpage https://immersive-web.github.io/webxr-samples/360-photos.html demonstrates WebXR APIs. It has a photosphere built in WebGL, which places the user at the origin when observed inside VR mode.

x3dom / x3dom