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 24772 - releasePointerCapture() should fail if called from a node that doesn't currently capture the pointer
Summary: releasePointerCapture() should fail if called from a node that doesn't curren...
Status: CLOSED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-22 00:06 UTC by Jacob Rossi [MSFT]
Modified: 2014-03-05 17:51 UTC (History)
1 user (show)

See Also:

Attachments

Description Jacob Rossi [MSFT] 2014-02-22 00:06:17 UTC 
Example: http://jsfiddle.net/2wV8z/6/

1. A.setPointerCapture(pointerId);
2. B.releasePointerCapture(pointerId); //Should fail silently

Pointed out by romaxa working on Gecko implementation.
Comment 1 Jacob Rossi [MSFT] 2014-03-03 19:23:35 UTC 
Proposed spec text:

In Section 10.2 ("Releasing Pointer Capture"), insert a new step between the current steps 2 and 3 that reads:

"If the 'pointer capture target override' for the specified pointerId is not the Element on which this method was invoked, then terminate these steps."
Comment 2 Jacob Rossi [MSFT] 2014-03-05 17:51:29 UTC 
Changed as discussed in 3/4 telecon and proposed below:
https://dvcs.w3.org/hg/pointerevents/rev/f25bdc60c9a6