Bug 20108 - Clarify pointer capture behavior
Clarify pointer capture behavior
Status: RESOLVED FIXED
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification
unspecified
PC Windows NT
: P2 normal
: ---
Assigned To: Jacob Rossi [MSFT]
This bug has no owner yet - up for the taking
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-28 01:09 UTC by Jacob Rossi [MSFT]
Modified: 2012-12-09 00:58 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jacob Rossi [MSFT] 2012-11-28 01:09:31 UTC
Opening on behalf of Brandon Wallace: 

http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0003.html

Recommended details to add (based on IE10's implementation):

  1.  You can only capture a pointer if buttons>0 (e.g. mouse button is down, finger is on screen, or pen tip is on digitizer). So you can't just spy on interactions with UI outside your scope.
  2.  Once you set capture to a pointer, its target property will always be the capturing element. So while you can monitor movement of the pointer outside your contact (again, only while it's down), you can't get references to elements, etc.
  3.  Capture is automatically release when the pointer comes up (e.g. buttons==0).
  4.  Pointer events are not dispatched to elements not in the document.
Comment 1 Jacob Rossi [MSFT] 2012-11-28 01:12:09 UTC
5. Compatibility mouse events are also redirected to the capture element.
Comment 2 Jacob Rossi [MSFT] 2012-12-09 00:58:53 UTC
Fixed as suggested per 12/4 telecon resolution.

RESOLUTION: http://lists.w3.org/Archives/Public/public-pointer-events/2012OctDec/0091.html

http://dvcs.w3.org/hg/pointerevents/rev/fcbbeab23783