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.

Agree, I'll remove the event fire description here and add the reference to algorithm of requestPointerLock for providing detail.

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

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