- From: Marcos Cáceres <notifications@github.com>
- Date: Wed, 25 Oct 2023 15:08:45 -0700
- To: w3c/pointerlock <pointerlock@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 25 October 2023 22:08:51 UTC
@marcoscaceres commented on this pull request. > - to using the keyboard to move the magnified point of focus around - instead. When a pointerlockchange event is fired, web browsers - therefore need to make sure the event is communicated to assistive - technologies like screen magnifiers. - </p> + <section> + <h3> + The <dfn>pointer lock state</dfn> definition + </h3> + <p> + The [=pointer lock state=] is the state where a single DOM element, + which we will call the <dfn>pointer-lock target</dfn>, receives all + mouse events and the cursor is hidden. + </p> + <p> + Once in the [=pointer lock state=] the [=user agent=] has a can we split these definitions into three sentences maybe? There is too much information packed into this paragraph. -- Reply to this email directly or view it on GitHub: https://github.com/w3c/pointerlock/pull/49#pullrequestreview-1698324133 You are receiving this because you are subscribed to this thread. Message ID: <w3c/pointerlock/pull/49/review/1698324133@github.com>
Received on Wednesday, 25 October 2023 22:08:51 UTC