It may be helpful to add browser section to readme which describes browser compatibility.

Currently WebXR extension targets only Three.js VR examples for now (v0.1.0). So WebXR polyfill supports only part of WebXR APIs now.

I think WebXR Samples would be good as next target.

https://immersive-web.github.io/webxr-samples/

Most of the examples doesn't seem to work correctly with the extension now.

Maybe related to: #6

Currently when Google cardboard is selected the "translate/rotate" option is still available, it should be hidden and set by default rotation (on all the 3dof headsets), the same goes for 3dof controllers.

Make extension icon showing the right top in browser.

Storage API I use is async method so configuration set up is done asynchronously. I'd like to investigate how to complete configuration setup before application starts for robust use.

Currently emulated devices are OculusGo and Quest. Users may think that this extension is Oculus device specific. To avoid such an impression, it may be good to add non-Oculus devices.

If we make an instruction video including

• How to install
• How to boot up
• How to select devices
• How to control devices
• etc

users can easily understand

• they don't need their own XR device
• they can run WebXR application on desktop browser
• what they can do with the extension
• how to use
• etc

Now we have animation gif in readme but perhaps it isn't good enough.

The video can be long so I'm thinking on uploading to YouTube (or somewhere). If we do so, should we upload to Mozilla Mixed Reality YouTube playlist?

Currently when changing the device it doesn't seem to do anything, for example if I change from a device to none It should throw the events of device disconnected or so, so things updated around, or force the user to refresh the page or show one info message indicating it.

Some WebXR API needs to recognize XR device, for example supportsSession(mode) checks if device supports the specified mode. Probably need to investigate how emulated XR device can be recognized by WebXR API supported by browser.

Currently controller emulator UI is

• Space: Trigger button
• Cursors: Controller rotation

But I think I can improve, for example using mouse or visualize as WebVR emulator does?

Currently projectionMatrix is hard coded. XRRenderState should take option parameters and projectionMatrix should be calculated from them

https://www.w3.org/TR/webxr/#xrrenderstate-interface

It seems the emulator doesn't work on the latest Chrome (Version 76.0.3809.100 (Official Build) (64-bit)) under origin trial.

The root issue seems that WebXR API is enabled by default and Chrome defines XR* (and navigator.xr) asynchronously. WebXR polyfill defines them synchronously and then they're overriden by Chrome later. (Currently) this extension can't interact with WebXR API defined by browser then fails to run.

Workaround for now may be disabling WebXR API via chrome://flags.

Maybe Related: #34

Update: I investigated the root issue and realized what I wrote above doesn't seem correct. It's actually that they're defined synchronously but done after "run_at": "document_start" of content scripts. So custom XR* defined in content scripts are overriden by browser. navigator.xr doesn't seem to be overriden.

This issue follows #40

In visual controls, it looks good if we use headset/controllers assets looking like the emulated devices.

Probably using https://github.com/immersive-web/webxr-input-profiles is good if assets are added?

Currently controller emulator only one controller (right controller). Supporting two controllers may be useful.

Currently only supports one trigger button. We should support more various type of buttons, for example Oculus Go tough pad(?).

Maybe related to #15

https://github.com/immersive-web/webxr-polyfill

The problems are

• WebXR API webxr-polyfill follows is old (Updated)
• How can I inject webxr-polyfill code to content_script?
• How can the emulator interact with? For example, when button is pressed how can we fire select event of polyfill?

Device transforms aren't stored so for example if you reopen development tool their transforms are reset to default. Storing/restoring them may be helpful.

For cases where you maybe already have webxr in your system and want to use it instead of the extension. It could be nice to have it available on the pop up menu when clicking the extension icon

"1. Immersive VR Session" in https://immersive-web.github.io/webxr-samples/ tries to render only in XR device by setting session.updateRenderState({ baseLayer: new XRWebGLLayer(session, gl) }); and not appending the canvas to a page. Where should we render in immersive mode for such an application?

Currently we expect the canvas is appended to a page and render into it even in immersive mode. User can't see anything if the canvas isn't appended.

Currently XRSession.updateRenderState() renew state.

updateRenderState(option) {
  this.renderState = new XRRenderState(option);
}

But it should update.

Josh do a UX analysis to figure out the UI we need for phase one of this project. Should include a mock-up if what it could look like.

Currently changing emulation device and stereo effect on the devtool panel requires reloading the application page. It may be useful to support direct emulation device change without reloading.

Currently I just set a certain default position. I think we should set more appropriate values.

The controller button can have two status. The button is being pressed or not. But there is no change in "WebXR" panel in developer tool even if user presses/releases the button. I think it's helpful if user can know the button is being pressed or not. For example changing the controller color while button is being pressed?

Currently device profiles are scattered across configuration.js, device-manager.js, and so on. Maybe better to define at a single place and refer from others.

• Oculus Go
• Oculus Quest
• HTC Vive
  ... adding later

https://addons.mozilla.org/en-US/firefox/
https://chrome.google.com/webstore/category/extensions

Currently user can control headset/controller only with keys. We may want to add visual controller (Three.js transform controls) as WebVR emulator does.

https://github.com/spite/WebVR-Extension

Currently polyfill.js supports only part of WebXR API

Related: #3, #34

So people could get an idea of what they are doing without reading the doc

Something fancier than XR could be nice

Ideally we will have a gltf for each device, but in the meantime we could use a generic VR input device like https://poly.google.com/view/cUT5C1Krx7g or https://poly.google.com/view/0n5B6e5lYZe

The ability would be helpful. For example, developers can use it for automatic test.

Currently user can control headset/controller only with keys. We may want to add mouse controls in which headset/controller follows mouse pointer.

The current code is very dirty and hacky

Error message.

Uncaught ReferenceError: browser is not defined

content-script.js:27 (anonymous function)

browser.storage.local.get(configurationId).then(result => {

Add non-stereo but controller activated mode. Maybe useful not to test but enjoy immersive application on desktop.

• Extension on/off
• Configure UI
• Select Headset/Controller device
• etc

Move this repository under immersive-web (or somewhere) if needed. See immersive-web/proposals#53

For example when working with a 6dof + 2x6dof controllers, a lot of arrows appear on the screen for all the gizmos and it's hard to choose the one you are interested, for example if you want to focus on the headest or one controller.
It could be nice to hide the other gizmos just by focusing on an actual device at time, ideally adding some shortcut too, like 1: headset, 2: controller1, 3: controller2 or so

Just they render black screen in immersive mode.