You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If someone calls vrDisplay.requestPresent() and it rejects (or possibly if it throws too), I would hope for an event to fire. Otherwise, I'll have to rely on Promises entirely and interface with these methods directly, at which point the events become not that useful.
The text was updated successfully, but these errors were encountered:
To be honest I'd prefer to reply on the promise entirely, but that's not a viable option for vrdisplaypresentchange. The issue is that the browser may force you our of VR presentation at any time for any reason (most likely the user hit some explicit "Exit WebVR" button, like tapping esc to exit fullscreen). We can add an error event, certainly, but I don't see it filling an explicit need like the presentchange event does.
For measure, the Fullscreen API has the following events:
fullscreenchange
fullscreenerror
For the WebVR API, we have
vrdisplaypresentchange
- should we support this?vrdisplaypresenterror
If someone calls
vrDisplay.requestPresent()
and it rejects (or possibly if it throws too), I would hope for an event to fire. Otherwise, I'll have to rely on Promises entirely and interface with these methods directly, at which point the events become not that useful.The text was updated successfully, but these errors were encountered: