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

@james-howard commented on this pull request.

I added one small grammar comment, but otherwise looks good to me.

> -            This prevents locking upon initial navigation or re-acquiring lock
-            without user's attention.
-          </p>
-          <p>
-            A {{requestPointerLock()}} call immediately after the <a>default
-            unlock gesture</a> MUST fail even when <a>transient activation</a>
-            is available, to prevent malicious sites from acquiring an
-            unescapable locked state through repeated lock attempts. On the
-            other hand, a {{requestPointerLock()}} call immediately after a
-            programmatic lock exit (through a {{Document/exitPointerLock()}}
-            call) MUST succeed when <a>transient activation</a> is available,
-            to enable applications to move frequently between interaction
-            modes, possibly through a timer or remote network activity.
+            A [=parallel queue=] named as <dfn>lock requests queue</dfn> is
+            used for queuing all requests. When <dfn>requestPointerLock()</dfn>
+            invoked, perform the following steps:

*is* invoked

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

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