25147 2014-03-25 18:16:10 +0000 What should happen when element.setPointerCapture is called while the pointer is already being captured? 2014-06-03 05:26:03 +0000 1 1 1 Unclassified PointerEventsWG Pointer Events specification unspecified PC Linux RESOLVED FIXED P2 normal --- 1 bugs jrossi nekr.fabula public-pointer-events public-pointer-events-bugzilla oldest_to_newest 102891 0 bugs 2014-03-25 18:16:10 +0000 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. 103858 1 jrossi 2014-04-15 04:42:32 +0000 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). 107175 2 jrossi 2014-06-03 05:26:03 +0000 Fixed in resolution to Bug 24971 https://dvcs.w3.org/hg/pointerevents/rev/06a63f400a2a