- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 25 Oct 2023 15:17:14 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/pointerlock/pull/49/review/1698332170@github.com>
@marcoscaceres commented on this pull request. > + a {{PointerLockOptions}} and a <dfn>cursor position</dfn> which is a + pair of numbers representing the location of the system mouse cursor + when the Pointer Lock State was entered (the same location that is + reported in `screenX`, `screenY`). The [=pointer-lock target=] must + receive all relevant user generated {{MouseEvent}} events: namely, + all user-generated `mousemove`, `mousedown`, `mouseup`, `click`, + `dblclick`, `auxclick`, and `wheel` [[ui-events]]. No other elements + may receive these events while in [=pointer lock state=]. There will + be no dispatching of events that require the concept of a mouse + cursor: namely, `mouseenter`, `mouseleave`, `mouseover`, `mouseout`, + `drag`, and `drop`. + </p> + <p> + While in the [=pointer lock state=] if the [=pointer-lock options=]' + {{PointerLockOptions/unadjustedMovement}} member is `true` the event + coordinates must not be affected by the underlying platform behaviors This has to be a statement of fact. This is not testable I don't think. ```suggestion coordinates will not be affected by the underlying platform behaviors ``` -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#pullrequestreview-1698332170 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/1698332170@github.com>
Received on Wednesday, 25 October 2023 22:17:19 UTC