[Bug 25147] What should happen when element.setPointerCapture is called while the pointer is already being captured?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25147

--- Comment #1 from Jacob Rossi [MSFT] <jrossi@microsoft.com> ---
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).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 15 April 2014 04:42:33 UTC