- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 25 Oct 2023 15:44:25 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 October 2023 22:44:30 UTC
@marcoscaceres 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.
Oh, lol, ok it's done in the next paragraph... can we move this up and make it an algorithm?
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/pull/49#discussion_r1372393436
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/pointerlock/pull/49/review/1698356172@github.com>
Received on Wednesday, 25 October 2023 22:44:30 UTC