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

@mustaqahmed commented on this pull request.



> +      <section>
+        <h3>
+          The <dfn>Pointer Lock State</dfn> Definition
+        </h3>
+          <p><a>Pointer Lock State</a> is the state where a single DOM element, which
+            we will call the <dfn>pointer-lock target</dfn>, receives all mouse events and the cursor
+            is hidden.</p>
+          <p>
+            Once in the <a>Pointer Lock State</a> the <a>user agent</a> has a
+            <a>pointer-lock target</a> and a set of <a>PointerLockOptions</a>. The
+            <a>pointer-lock target</a> must receive all relevant user generated
+            {{MouseEvent}} events (for example: `mousemove`, `mousedown`, `mouseup`, 
+            `click`, and `wheel`) [[ui-events]]. No other elements may receive these
+            events while in <a>Pointer Lock State</a>. Events that require the concept of
+            a mouse cursor must not be dispatched (for example: `mouseover`, `mouseout`,
+            `drag`, and `drop`).

@alvinjiooo Please add a link here to this issue I just filed: https://github.com/w3c/pointerlock/issues/97

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

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