Re: [w3c/pointerlock] Add lock options to requestPointerLock (#49)

@mustaqahmed commented on this pull request.



> -        appropriate name with its <code>bubbles</code> attribute [[DOM]] set to
-        false to the pointer lock <a>target</a> element's [=Node/node
-        document=].
-      </p>
-      <p class="note">
-        Magnification software increases the size of content on the screen. It
-        uses the mouse to move the magnified point of focus around. When a
-        pointer lock is initiated, the magnification software needs to switch
-        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>
+      <dl>
+        <dt>
+          <dfn>Engagement gesture</dfn>

Please drop the "engagement gesture" glossary entry and all references to it.  It was removed from the spec in https://github.com/w3c/pointerlock/pull/76.

The term "transient activation" in the current spec captures the same idea.  In "algorithmic" spec language, this is like "the 'relevant global object' having 'transient activation'...".

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

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