When a subsequent requestPointerLock is rejected, should an already locked target exit lock state? · Issue #91 · w3c/pointerlock (original) (raw)
Description
opened
In the PR #49's algorithm of requestPointerLock is currently missing the description for the scenario:
When a subsequent request failed (for any possible reason), should an already locked target exit lock state?
Metadata
Metadata
Assignees
No one assigned
Labels
No labels
No labels
Type
No type
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests