[Bug 24923] What should happen to the mouse events if pointer event listener removes the target from document or hides it?

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

--- Comment #11 from Jacob Rossi [MSFT] <jrossi@microsoft.com> ---
I strongly want to avoid hit testing again for compatibility mouse events.
Primarily for perf reasons, but also because we saw developer confusion when
pointer* and mouse* didn't go to the same element (an early preview of IE10
behaved this way).

This behavior is defined at the top of the section:

"Unless otherwise noted, the target of any mapped mouse event MAY be the same
as the target for the pointer event from which it was mapped."

(MAY is used here as the entire section is optional)

Now, in the case of node removal, IE will fix up the target to its parent in
the propagation path of the event.  This works well with most coding patterns
similar to what Scott describes. In the case that the mouseup handler is on the
node removed...we'll, I think you shot yourself in the foot. :-)

Do we want spec text to describe this fix up behavior?  I apologize that this
nuance was left out of our spec proposal (this scenario doesn't come up often).

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

Received on Tuesday, 11 March 2014 05:39:41 UTC