This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25147 - What should happen when element.setPointerCapture is called while the pointer is already being captured?
Summary: What should happen when element.setPointerCapture is called while the pointer...
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-25 18:16 UTC by Olli Pettay
Modified: 2014-06-03 05:26 UTC (History)
2 users (show)

See Also:

Attachments

Description Olli Pettay 2014-03-25 18:16:10 UTC 
https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#setting-pointer-capture
doesn't say anything about this case.

Bug 24971 is related, but not the same issue.
Comment 1 Jacob Rossi [MSFT] 2014-04-15 04:42:32 UTC 
The proposal in Comment 5 of Bug 24971 would address this:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24971#c5

setPointerCapture/releasePointerCapture set and clear the "pending" capture node.

Capture is changed to the "pending" capture node ( and gotpointercapture/lostpointercapture fired) when a UA is to fire the next pointer event for the pointer.

Thus, multiple calls before the next event are essentially coalesced to one change of capture. Furthermore, calling elm.setPointerCapture(id) when elm already is the capture node for the pointer does not generate a change of capture (or the got/lost events).
Comment 2 Jacob Rossi [MSFT] 2014-06-03 05:26:03 UTC 
Fixed in resolution to Bug 24971
https://dvcs.w3.org/hg/pointerevents/rev/06a63f400a2a