Interactions with the scene don't work in Looking Glass popup

[hybridherbst]

Turns out interacting with the scene doesn't really work in the popup: a new camera is constructed that the app around doesn't know of and can't really access, and there's no XR controller based on the mouse interactions with the popup.

Options here could be:

• allow attaching to that created camera (see #17)
• properly pass through mouse data on the popup as a XR Controller, probably screen-based, similar to how touch is handled on mobile AR scenarios.

[BryanChrisBrown]

we've got an open PR open here that we're investigating, ideally we'd like to be able to duplicate the events from the original events on the new looking glass canvas, however it's proven a bit tricky to duplicate or send events to other locations. https://github.com/Looking-Glass/looking-glass-webxr/pull/7

I've got an example here that shows how to modify the config values via code: https://codesandbox.io/s/bouncy-watch-looking-glass-kbf8k5

[hybridherbst]

I think this depends a bit on whether you see Looking Glass as a second screen (independent interactions possible) or a pure output device (always cloning the main screen).

[BryanChrisBrown]

ah I see, handling input from the main screen can also be desirable, I'll have to see what we can do with the webXR pipeline to enable this, I think both use cases here (main & secondary) display are valid uses.

[hybridherbst]

Something like the spectator sample would be nice: https://immersive-web.github.io/webxr-samples/spectator-mode.html