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

@marcoscaceres commented on this pull request.



> +          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`.

This is a statement of fact: 

```suggestion
          reported in `screenX`, `screenY`). The [=pointer-lock target=]
          receives all relevant user generated {{MouseEvent}} events: namely,
          all user-generated `mousemove`, `mousedown`, `mouseup`, `click`,
          `dblclick`, `auxclick`, and `wheel` [[ui-events]]. No other elements
          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`.
```

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

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