Basically this is what I said in
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0978.html. But
your pros & cons summarize it nicely.
2011/8/29 Glenn Maynard
> On Mon, Aug 22, 2011 at 8:13 PM, Vincent Scheib wrote:
>
>> What are the units of .movementX/Y if we're reading 'raw' inp
> -- Provide mouse deltas without hiding the cursor, alternatively provide a
> bounding rectangle for mouse --
> (See Klaas's recent suggestions)
> It may be possible, but significant implementation hurdles remain for
this.
> First, we must be able to specify the units that mouse deltas will be
pr
You could constrain the mouse cursor on linux using a combination of
XQueryPointer and XWarpPointer. By moving the cursor when it hits the edge
of an element.
The same solution could be used for Mac where there also doesn't seem to be
a direct method for constraining the mouse cursor. When search
I agree with you that the deltas should be in a separate event. That would
also be the most logical because moving the cursor(corresponding to a
"mousemove" event) and physically moving your mouse are separate things. If
"mousemove" wasn't already used for cursor movement("mousemove" imo should
hav
possibly could undermine that design?
So to summarize all the above, design to separate features: 1. an event for
getting mouse delta 2. an API for walling the mouse to an element.
Klaas Heidstra
> A few comments:
>
> Is there a need to provide mouse-locking on a per-element basis? It seems
to
