W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: Mouse Lock

From: timeless <timeless@gmail.com>
Date: Thu, 23 Jun 2011 21:29:07 -0400
Message-ID: <BANLkTimKQEbq_1gagEW8ZDa+qxCegFr4bA@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>, Olli@pettay.fi, Jonas Sicking <jonas@sicking.cc>, Adam Barth <w3c@adambarth.com>, Vincent Scheib <scheib@google.com>, Brandon Andrews <warcraftthreeft@sbcglobal.net>, "Gregg Tavares (wrk)" <gman@google.com>, Glenn Maynard <glenn@zewt.org>, Charles Pritchard <chuck@jumis.com>, Kenneth Russell <kbr@google.com>, robert@ocallahan.org, public-webapps@w3.org
And what if the device in question is just a touchscreen with no
keyboard, mouse or hardware buttons?

On 6/20/11, Tab Atkins Jr. <jackalmage@gmail.com> wrote:
> On Mon, Jun 20, 2011 at 3:03 PM, Olli Pettay <Olli.Pettay@helsinki.fi>
> wrote:
>> On 06/21/2011 12:25 AM, Tab Atkins Jr. wrote:
>>> The use-case is non-fullscreen games and similar, where you'd prefer
>>> to lock the mouse as soon as the user clicks into the game.  Minecraft
>>> is the first example that pops into my head that works like this -
>>> it's windowed, and mouselocks you as soon as you click at it.
>> And how would user unlock when some evil sites locks the mouse?
>> Could you give some concrete example about
>> " It's probably also useful to instruct the user how to release the lock."
> I'm assuming that the browser reserves some logical key (like Esc) for
> releasing things like this, and communicates this in the overlay
> message.
> ~TJ

Sent from my mobile device
Received on Friday, 24 June 2011 01:29:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:20 UTC