Clarify seamless VR link traversal #3994
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We should make it clear that the VR experience is only seamless on Vive et al. We are not managing our user's expectations correctly, see aframevr#1473
dmarcos
reviewed
Feb 4, 2019
|
I see. I still think it's confusing: if you use Firefox mobile for cardboard VR, or Firefox desktop for a fullscreen 2D experience, you still get bounced out of VR/fullscreen. |
|
Fullscreen API is not preserved by any browser on navigation. |
|
Added info in docs: Let me know if you are missing any other details |
|
Perfection! Thank you so much. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
We should make it clear that the VR experience is only seamless on Vive et al. We are not managing our user's expectations correctly, see #1473
Changes proposed: