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

@alvinjiooo commented on this pull request.



> +              If this value is set to `true`, then the pointer movements will
+              not be affected by the underlying platform modications such as
+              mouse accelaration.
+            </p>
+          </dd>
+        </dl>
+      </section>
+      <section>
+        <h3>
+          `pointerlockchange` and `pointerlockerror` Events
+        </h3>
+        <p>
+          Two events are used to communicate pointer lock state change or an
+          error in changing state. They are named <dfn>pointerlockchange</dfn>
+          and <dfn>pointerlockerror</dfn>. If pointer lock is entered or exited
+          for any reason a {{Document/pointerlockchange}} event must be sent.

I think these two events are more like consequences to the algorithm of "requestPointerLock". How about I add the reference and point it to the algorithm of "requestPointerLock"?
```
<p>
  The [=user agents=] must deliver these events by <a data-lt=
  "queue a task">queuing a task</a> to [=fire an event=] of the
  appropriate name with its `bubbles` attribute [[DOM]] set to false to
  the pointer lock [=Event/target=] element's [=Node/node document=]. Refer to algorithm of 
  [=requestPointerLock=] for detail. 
</p>
```


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

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