- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 18 Dec 2023 22:15:29 -0800
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 December 2023 06:15:36 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.
If we can avoid any duplication, all the better (i.e., make sure you only talk about firing the event in 1 place)
--
Reply to this email directly or view it on GitHub:
https://github.com/w3c/pointerlock/pull/49#discussion_r1430965794
You are receiving this because you are subscribed to this thread.
Message ID: <w3c/pointerlock/pull/49/review/1788170759@github.com>
Received on Tuesday, 19 December 2023 06:15:36 UTC