RE: Issue: Setting a capture on an offshore element

Hi Francois,

We opened Bug  21749 based on your feedback [1]. The proposal (comments 2 and 5 in the bug) is that:

1) calling setPointerCapture() on an element not in the document tree throws an exception
2) removing an element that currently has capture must clear the capture and cause a lostpointercapture event to be fired at the document (since input events do not generally get fired at orphaned elements)

Let us know if you think this change is acceptable. Thanks!

-Jacob

[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=21749

Received on Tuesday, 15 April 2014 05:30:07 UTC