- From: Navid Zolghadr via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 May 2016 17:51:51 +0000
- To: public-pointer-events@w3.org
NavidZ has just created a new issue for https://github.com/w3c/pointerevents: == How removing target in pointer event handler affects compat mouse event target == There is this paragraph in the spec: 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 ownerDocument'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) that still participates in its ownerDocument's tree**, meaning that a new event path (based on the new target node) is built for the mouse event. However the new target seems not to be correctly worded based on what Edge does and makes sense at least to me. Maybe the new target should be the "nearest ancestor node in the propagation path of the corresponding pointer event" instead. The difference is that if the pointer event handler reparents the target and then removes it from the document, the existing wording seems to imply that the mouse event target should be the new parent. But the new wording says it should be sent to the original parent. Here is an example: https://output.jsbin.com/mobeju Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/64 using your GitHub account
Received on Monday, 9 May 2016 17:51:54 UTC