fix(interaction): catch pointerlock failures#3546
Merged
Merged
Conversation
The catch handler silently handles pointer lock failures allowing interaction to proceed without causing application level disruption
|
🎉 This PR is included in version 36.2.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The catch handler silently handles pointer lock failures allowing interaction to proceed without causing application level disruption
Context
When pointer lock fails on an unsupported browser, the application would crash with an error. This change allows the application to proceed by silently catching the failure.
Results
Changes
PR and Code Checklist
npm run reformatto have correctly formatted codeTesting