<div>The spec should explicitly specify which MouseEvent properties are available during the various drag events to avoid assumptions.</div><div><br></div><div>Gecko currently sets pageX, clientX, screenX etc. to zero on the source node events (drag, dragend).</div>
<div><br></div><div>As far as I know there are no known security flaws surrounding this implementation. Browsers allow positioning values outside the browser window on mousemove events during a mousedown + mousemove operation.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">-----------------------</div><div class="gmail_quote"><br>This issue is related to whether or no a DragEvent is infact a MouseEvent.<div><br></div><div>The current drag specifies that "User agents must, every 350ms (±200ms), perform the
following steps in sequence.." It doesn't make sense to trigger this event if nothing has changed based on time alone. If something moves in front of it or behind it, it may need to be triggered again, but a user agent should be able to decide whether or not that's a possibility.</div>
<div><br></div><div>All current implementations trigger this sequence faster if the mouse is moving. Effectively treating mouse movements as new drag events. Just like mousemove.</div><div><br></div><div>IMO, it should be specified that mouse movements triggers a new iteration of this sequence, and that current mouse position should be a part of the event.</div>
<div><br></div><div>The specification is only partly input device agnostic. It can't be both totally input device agnostic and inherit MouseEvent. If it's going to inherit MouseEvent it needs to be specified what that means.</div>
<div><br></div><div>-----------------------</div><div><br></div><div>(This is a repost because the first two was blocked by mod filter, hopefully this doesn't become a double post.)</div></div>