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

@scheib 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

Full screen is explicitly not a requirement, as several use cases are common in non-fullscreened applications, e.g. 9.2, 9.4.  There are e.g. medical imaging applications that use it and should not be forced to be full screen.

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

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