Make vrdisplayactivate driven enter-vr path more robust

[dmarcos]

No description provided.

[dmarcos]

This is ready.

[gfodor]

qq on this -- is this patch dependent upon anything specific in super-three? we're looking to cherry pick this commit into our A-Frame fork which adds (hacky, not ready for PR) multiview support, but are hesitant to move over to super-three without more testing/validation. Thanks!

[dmarcos]

@gfodor super-three is stock THREE + PR waiting to merge upstream. At the moment mrdoob/three.js#16015, mrdoob/three.js#15347 and mrdoob/three.js#15290

Intent is always using stock THREE. If you can spare a comment on those PRs might help expedite merge and put us back on track.

[gfodor]

Cool. I upvoted the resolution one, which I've seen -- we haven't tried WebXR support yet so can't confirm the others but looks like others have.

…

On Sun, Mar 24, 2019 at 8:35 AM Diego Marcos ***@***.***> wrote: @gfodor <https://github.com/gfodor> super-three is stock THREE + PR waiting to merge upstream. At the moment mrdoob/three.js#16015 <mrdoob/three.js#16015>, mrdoob/three.js#15347 <mrdoob/three.js#15347> and mrdoob/three.js#15290 <mrdoob/three.js#15290> Intent is always using stock THREE. If you can spare a comment on those PRs might help expedite merge and put us back on track. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4093 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AANbdFfGeV0LGvd_JnjXXTai8_M2I2Exks5vZ5skgaJpZM4b9rs2> .