Add boundary events in implicit capture scenarios (#251)

NavidZ · patrickhlauke · commit 8381126021fe · 2018-04-26T02:16:11.000+01:00
* Add boundary events in implicit capture scenarios
diff --git a/index.html b/index.html
@@ -839,11 +839,20 @@ <h2><dfn>Implicit Pointer Capture</dfn></h2>
         </section>
         <section>
             <h3>Implicit Release of Pointer Capture</h3>
-            <p>Immediately after firing the <code>pointerup</code> or <code>pointercancel</code> events, a user agent MUST clear the <a>pending pointer capture target override</a> for the <code>pointerId</code> of the <code>pointerup</code> or <code>pointercancel</code> event that was just dispatched, and then run <a href="#process-pending-pointer-capture">Process Pending Pointer Capture</a> steps to fire <code>lostpointercapture</code> if necessary.</p>
-            <p>If the user agent supports firing the <code>click</code> event (see <a title="compatibility mouse events" href="#dfn-compatibility-mouse-events">compatibility mouse events</a>) and if in an implicit release scenario both <code>click</code> and <code>lostpointercapture</code> events are fired, <code>click</code> should be fired before <code>lostpointercapture</code>.</p>
+            <p>Immediately after firing the <code>pointerup</code> or <code>pointercancel</code> events,
+               a user agent MUST clear the <a>pending pointer capture target override</a>
+               for the <code>pointerId</code> of the <code>pointerup</code> or <code>pointercancel</code> event that was just dispatched,
+               and then run <a href="#process-pending-pointer-capture">Process Pending Pointer Capture</a> steps to fire <code>lostpointercapture</code> if necessary.
+               After running <a href="#process-pending-pointer-capture">Process Pending Pointer Capture</a> steps,
+               if the pointer supports hover, user agent MUST also send corresponding boundary events if necessary
+               to reflect the current position of the pointer with no capture. </p>
+            <p>If the user agent supports firing the <code>click</code> event
+               (see <a title="compatibility mouse events" href="#dfn-compatibility-mouse-events">compatibility mouse events</a>)
+               and if in an implicit release scenario both <code>click</code> and <code>lostpointercapture</code> events are fired,
+               <code>click</code> SHOULD be fired before <code>lostpointercapture</code>.</p>
             <p>When the <a>pointer capture target override</a> is removed from its <code>ownerDocument</code>'s tree,
-clear the <a>pending pointer capture target override</a> and <a>pointer capture target override</a> nodes
-and fire a PointerEvent named <code>lostpointercapture</code> corresponding to the captured pointer at the document.</p>
+               the <a>pending pointer capture target override</a> and <a>pointer capture target override</a> nodes SHOULD be cleared
+               and also a PointerEvent named <code>lostpointercapture</code> corresponding to the captured pointer SHOULD be fired at the document.</p>
             <p>When a pointer lock ([[!PointerLock]]) is successfully applied on an element, a user agent MUST run the steps as if the releasePointerCapture() method has been called if any element is set to be captured or pending to be captured.
 
         </section>
