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

@marcoscaceres commented on this pull request.



> +          <p>
+            Once in the <a>pointer lock state</a> the <a>user agent</a> has a
+            <a>pointer-lock target</a>, a <dfn>pointer-lock options</dfn>, which is a <a>PointerLockOptions</a> 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 <code>screenX</code>,
+            <code>screenY</code>). The <a>pointer-lock target</a> 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
+            <a>pointer lock state</a>. 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>
+            <dl data-dfn-for="PointerLockOptions" data-link-for=
+            "PointerLockOptions">
+              While in the <a>pointer lock state</a> if the <a>pointer-lock options</a>'
+              <a>unadjustedMovement</a> member is <code>true</code> the event 

When linking to WebIDL things, it's best to use the special WebIDL syntax.

```suggestion
              {{PointerLockOptions/unadjustedMovement}} member is `true` the event 
```

Please see our [WebIDL shorthands cheat sheet](https://respec.org/docs/#Shorthands-Guide). 

Be great to update the changes throughout this pull request 🙏 


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