search

immersive-web / webvr

Archival repository for the legacy WebVR Specification.
Other
13 stars 14 forks source link

Clarification on connection/disconnection behavior #10

Open toji opened 6 years ago

toji commented 6 years ago

From @NellWaliczek on October 15, 2016 2:28

Here are couple cases I'm curious about:

Case 1:

  1. The developer calls getVRDisplays() but does not maintain a reference to the VRDisplays returned
  2. The user unplugs one of the VRDisplays
  3. The developer calls getVRDisplays again

Is the unplugged VRDisplay in the sequence and marked isConnected==false? Or is it simply not present?

Case 2:

  1. The developer is holding a reference to a VRDisplay
  2. The user unplugs this VRDisplay
  3. The user plugs back in the same VRDisplay

Is a new VRDisplay object created or is the same object now just marked as isConnected==true. In other words, is VRDisplay.displayId consistent for a specific piece of hardware every time that hardware is attached?

Case 3:

  1. While in the middle of a frame, the user plugs in a new VRDisplay

When does the connected event fire? After the submitFrame() call but before the next RAF callback? Does it matter?

Copied from original issue: immersive-web/webxr#119