[Bug 21749] Setting a capture on an offshore element

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

--- Comment #2 from Jacob Rossi [MSFT] <jrossi@microsoft.com> ---
It's generally expected that DOM Events do not fire at orphaned elements. In
particular, this is because you can't form a proper event path for dispatch.

However, because the capture APIs exists, I do see that this could lead a
developer to believe capture could redirect events to an orphaned element. I'd
propose we add this exception to the spec.

My proposal is to add a step to the setPointerCapture() method that reads:

If the Element on which this method is invoked does not participate in its
ownerDocument's tree, throw an exception with the name "InvalidStateError".

Happy to let folks bikeshed on the specific exception to be thrown (IE
currently, oddly enough, does not throw a named exception in this case). :-)

I'm also not 100% confident on the spec language to denote an orphaned element.
Will want to check with someone like AnneVK to confirm.

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

Received on Tuesday, 11 March 2014 05:20:12 UTC