When a subsequent requestPointerLock is rejected, should an already locked target exit lock state?

w3c / pointerlock

Pointer Lock

https://w3c.github.io/pointerlock/

Other

17 stars 16 forks source link

When a subsequent requestPointerLock is rejected, should an already locked target exit lock state? #91

Open alvinjiooo opened 6 months ago

alvinjiooo commented 6 months ago

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?

scheib commented 5 months ago

My opinion is no, lock should not be exited due to a new request that can not be satisfied.

E.g. Attempting an upgrade from a default request to a request with unadjusted movement that can not be satisfied should not cause the earlier lock to be exited.