- From: Alvin Ji <notifications@github.com>
- Date: Mon, 30 Oct 2023 21:54:32 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/pointerlock/pull/49/review/1705444517@github.com>
@alvinjiooo commented on this pull request. > + 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 + such as mouse acceleration. In other words, UA must use the APIs + provided by the underlying platform to guarantee getting the raw + events. If the {{PointerLockOptions}}' + {{PointerLockOptions/unadjustedMovement}} member is `false` UA must + rely on the default behavior of the underlying platform regarding the + mouse acceleration. + </p> + <p> + In the [=pointer lock state=] the system mouse cursor must be hidden. How about: ``` In the [=pointer lock state=], the system mouse cursor is hidden and the window is prevented from losing focus, regardless of mouse movement or button presses. This is directly or indirectly achieved utilizing the underlying operating system API. ``` -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#discussion_r1377052746 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/1705444517@github.com>
Received on Tuesday, 31 October 2023 04:54:38 UTC