- From: Marcos Cáceres <notifications@github.com>
- Date: Thu, 26 Oct 2023 12:09:16 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 26 October 2023 19:09:21 UTC
@marcoscaceres commented on this pull request. > + <aside class="note"> + <p> + This ensures a user can leave a document that constantly + attempts to lock the pointer. The document will be blocked + from locking upon initial navigation or re-acquiring lock + unless the user re-engages directly with the document. + </p> + <p> + Conversely, if pointer lock is exited via + {{Document/exitPointerLock()}} no [=engagement gesture=] is + required to reenter pointer lock. This enables applications + that frequently move between interaction modes, and ones that + may do so based on a timer or remote network activity. + </p> + <p> + Pointer lock is commonly combined with fullscreen We should consider a provision that full screen may be required. It seems kinda bad that you can use this API without first being in full screen. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#pullrequestreview-1700471010 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/1700471010@github.com>
Received on Thursday, 26 October 2023 19:09:21 UTC