index.html
changeset 26 6543d83c0b74
parent 25 86bc101925d8
child 27 1c50a17098b5
     1.1 --- a/index.html	Fri Mar 15 11:49:34 2013 -0700
     1.2 +++ b/index.html	Fri Mar 15 15:15:10 2013 -0700
     1.3 @@ -173,7 +173,8 @@
     1.4  
     1.5        <p>Two events are used to communicate pointer lock state change or
     1.6        an error in changing state. They are named <dfn>pointerlockchange</dfn>
     1.7 -      and <dfn>pointerlockerror</dfn>.</p>
     1.8 +      and <dfn>pointerlockerror</dfn>. If pointer lock is entered or exited
     1.9 +      for any reason a <a>pointerlockchange</a> event must be sent.</p>
    1.10  
    1.11        <p><a>User agents</a>
    1.12        must deliver these events by <a
    1.13 @@ -210,14 +211,18 @@
    1.14            active sandboxing flag set</a> does not have the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html#sandboxed-pointer-lock-browsing-context-flag">
    1.15            sandboxed pointer lock browsing context flag</a> set.
    1.16  
    1.17 -          <p>Pointer lock must succeed only if the window is in focus and the
    1.18 -          user-agent is the active application of the operating system. The
    1.19 -          <a>target</a> element need not be in focus.</p>
    1.20 -
    1.21 -          <p>Pointer lock must succeed only if the <a>target</a> is in the DOM
    1.22 -          tree.  If the <a>target</a> is removed from the DOM tree after pointer
    1.23 -          lock is entered then pointer lock will be lost and a
    1.24 -           <a>pointerlockchange</a> event sent.</p>
    1.25 +          <p>Pointer lock must succeed only if the <a>target</a> is
    1.26 +          <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#in-a-document">in</a>
    1.27 +          the
    1.28 +          <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#active-document">active document</a>
    1.29 +          of a
    1.30 +          <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context">browsing context</a>
    1.31 +          which is (or has an
    1.32 +          <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#ancestor-browsing-context">ancestor browsing context</a>
    1.33 +          which is) in focus by a window which is in focus by the
    1.34 +          operating system's window manager. The <a>target</a> element and its
    1.35 +          <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context">browsing context</a>
    1.36 +          need not be in focus.</p>
    1.37  
    1.38            <p>If any element (including this one) in the same document
    1.39            is already locked (or pending lock) the pointer
    1.40 @@ -351,8 +356,14 @@
    1.41        <p>The Pointer Lock API must be agnostic to the underlying system-specific
    1.42        pointer locking mechanism.</p>
    1.43  
    1.44 -      <p>The Pointer Lock API must exit the pointer lock state if the <a>user agent</a>,
    1.45 -      window, or tab loses focus.</p>
    1.46 +      <p>The Pointer Lock API must exit the pointer lock state if the
    1.47 +      <a>target</a> is removed from its document, or the <a>user agent</a>,
    1.48 +      window, or tab loses focus. Moving focus between elements of
    1.49 +      <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#active-document">active documents</a>,
    1.50 +      including between
    1.51 +      <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#browsing-context">browsing contexts</a>,
    1.52 +      does not exit pointer lock. E.g. using the keyboard
    1.53 +      to move focus between contents of frames or iframes will not exit.</p>
    1.54      </section>
    1.55  
    1.56      <section class='informative'>