<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">> The spec should explicitly specify which MouseEvent properties are<br>
> available during the various drag events to avoid assumptions.<br>
<br>
</div>The spec requires them to all be set on all drag events, currently.<br><div class="im"></div></blockquote><div><br></div><div><div>I thought that this was clear too but apparently it's not clear that they should be set to something useful:</div>
<div><br></div><div><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=505521">https://bugzilla.mozilla.org/show_bug.cgi?id=505521</a></div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">
> The specification is only partly input device agnostic. It can't be both<br>
> totally input device agnostic and inherit MouseEvent. If it's going to<br>
> inherit MouseEvent it needs to be specified what that means.<br>
<br>
</div>I've added more text to clarify what it means in the case of the mouse not<br>
being used.<br>
<br></blockquote></div><br><div>Apparently it also needs to be clear that the properties SHOULD be set, if a pointing device IS being used. See above conversion on the Mozilla bug.</div><div><br></div><div>I'd suggest you add something like "If there is a relevant pointing device, the attributes should be set to relevant position values for all events in the sequence." - So that the intention is clear and don't have to rely on implicit interpretation.</div>