- From: Alvin Ji <notifications@github.com>
- Date: Tue, 28 May 2024 14:33:03 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 28 May 2024 21:33:07 UTC
@alvinjiooo 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`). Done -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#discussion_r1617913973 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/2083885672@github.com>
Received on Tuesday, 28 May 2024 21:33:07 UTC