- From: <bugzilla@jessica.w3.org>
- Date: Tue, 30 Sep 2014 15:38:41 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26934
scheib@chromium.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |scheib@chromium.org
--- Comment #1 from scheib@chromium.org ---
There's nothing fundamentally wrong with pointer lock targeting any element.
Specifying the element must be in the document easily handles any kind of
navigation concerns (where lock must be released) and dismiss any open ended
questions about where events are headed if elements aren't in the document.
Here are the relevant sections of Pointer Lock:
"""
5.1 Methods
requestPointerLock
...
Pointer lock must succeed only if the target is in the active document of a
browsing context which is (or has an ancestor browsing context which is) in
focus by a window which is in focus by the operating system's window manager.
...
8 Requirements
Pointer lock must be exited if the target is removed from its document, or the
user agent, window, or tab loses focus. Moving focus between elements of active
documents, including between browsing contexts, does not exit pointer lock.
E.g. using the keyboard to move focus between contents of frames or iframes
will not exit.
"""
And here is a draft of a change to add shadow tree/host to the sections:
"""
5.1 Methods
requestPointerLock
...
Pointer lock must succeed only if the target is in the active document (or a
shadow tree of a shadow host in the active document) of a browsing context
which is (or has an ancestor browsing context which is) in focus by a window
which is in focus by the operating system's window manager.
...
8 Requirements
Pointer lock must be exited if any of the follow occur:
- The target is removed from its document.
- The target is removed from its shadow tree.
- The user agent, window, or tab loses focus.
Moving focus between elements of active documents, including between browsing
contexts, does not exit pointer lock. E.g. using the keyboard to move focus
between contents of frames or iframes will not exit.
"""
Review & comments please.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 September 2014 15:38:46 UTC