- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 25 Oct 2023 15:56:54 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 October 2023 22:57:00 UTC
@marcoscaceres commented on this pull request. > + <p> + The process of exiting pointer lock, given an element, is as follows: + </p> + <ol> + <li>The system mouse cursor must be displayed again and positioned at + [=cursor position=] + </li> + <li>[=Queue an element task=], given this element, on the [=user + interaction task source=] to do the following: + <ol> + <li>[=Fire an event=] named {{pointerlockchange}} at the given + element's [=Node/node document=] + </li> + </ol> + </li> + <li>Exit the [=pointer lock state=] by setting [=pointer-lock I wish we had these as internal slots that are set... would be much nicer but this is just a nit. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#pullrequestreview-1698366026 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/1698366026@github.com>
Received on Wednesday, 25 October 2023 22:57:00 UTC