Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49)

@alvinjiooo commented on this pull request.



>            <aside class="note">
-            When a single <a>user activation</a> initiates both pointer lock
-            and fullscreen [[FULLSCREEN]], the {{requestPointerLock()}} call
-            succeeds only when it is made before a fullscreen request because
-            fullscreen is a <a>transient activation-consuming API</a>.
+            This algorithm is under active development and may be modified in

Issue #96 is created and associated in step 7 of the algorithm.

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

Message ID: <w3c/pointerlock/pull/49/review/2083631681@github.com>