- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Jun 2014 06:40:40 +0000
- To: public-pointer-events-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24923 --- Comment #22 from Patrick H. Lauke <redux@splintered.co.uk> --- combining my suggestions from the mailing list - and some additional note about the event path thing - here, I'd suggest changing the second line from <p>Unless otherwise noted, the target of any mapped mouse event SHOULD be the same target as the respective pointer event unless the target is no longer participating in its <code>ownerDocument</code>'s tree. In this case, the mouse event should be fired at the original target's parent node at the time it left the tree (meaning, a new even path is built for the mouse event).</p> to <p>Unless otherwise noted, the target of any mapped mouse event SHOULD be the same target as the respective pointer event, unless the target is no longer participating in its <code>ownerDocument</code>'s tree. In this case, the mouse event should be fired at the original target's nearest ancestor node (at the time it was removed from the tree), meaning that a new event path (based on the original path) is built for the mouse event.</p> -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 3 June 2014 06:40:43 UTC