There are some things need to do: 1. Implement VR process based on mozilla::ipc::GeckoChildProcessHost and mozilla::ipc::ProcessChild to define the bridge from content processes. Probably, we need to connect it with VSyncBridge as well. 2. Launch VR process when we are accessing VR content from the content process. 3. We can give a preference like "dom.vr.process.enabled" to turn on/off VR process for the current experiment and support some platforms which don't want VR be move to a separate process.
You need to log in before you can comment on or make changes to this bug.