[w3c/pointerlock] When a subsequent requestPointerLock is rejected, should an already locked target exit lock state? (Issue #91)

In the PR #49's algorithm of `requestPointerLock` is currently missing the description for the scenario:
When a subsequent request failed (if any possible reason), should an already locked target exit lock state? 
 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/issues/91
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/pointerlock/issues/91@github.com>