- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 22 Jun 2011 07:53:35 -0700
- To: Glenn Maynard <glenn@zewt.org>
- Cc: Simon Pieters <simonp@opera.com>, Aryeh Gregor <Simetrical+w3c@gmail.com>, Adam Barth <w3c@adambarth.com>, Vincent Scheib <scheib@google.com>, Brandon Andrews <warcraftthreeft@sbcglobal.net>, "Gregg Tavares (wrk)" <gman@google.com>, Charles Pritchard <chuck@jumis.com>, Kenneth Russell <kbr@google.com>, robert@ocallahan.org, public-webapps@w3.org
On Wed, Jun 22, 2011 at 2:54 AM, Glenn Maynard <glenn@zewt.org> wrote: > Unrelated, another detail: if most implementations are going to need to warp > the mouse cursor to do this, the other mouse event coordinates should always > be 0 (or null). Otherwise, implementations on platforms which don't need to > warp the cursor may still fill these in, causing incompatibilities. Events > like mouseover should probably be suppressed, too. At that point, it's > probably cleaner to stop firing *all* mouse movement events entirely, as if > the mouse isn't moving, and to use a separate "mousedelta" event when locked > which only has "deltaX" and "deltaY". I had this thought initially, but didn't pursue it. Now that you bring it up again, though, I think I agree. ~TJ
Received on Wednesday, 22 June 2011 14:54:22 UTC