W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: Mouse Capture for Canvas

From: Robert O'Callahan <robert@ocallahan.org>
Date: Thu, 10 Feb 2011 16:52:18 +1300
Message-ID: <AANLkTi=1OCCqAOyrouq30VjLh+Aj0p-t6Kw+HC1q1_DF@mail.gmail.com>
To: Brandon Andrews <warcraftthreeft@sbcglobal.net>
Cc: Kenneth Russell <kbr@google.com>, public-webapps@w3.org
On Wed, Feb 9, 2011 at 3:55 PM, Brandon Andrews <
warcraftthreeft@sbcglobal.net> wrote:

> Actually this would be used for both fullscreen and non-fullscreen
> applications.
> The reason for this is because it's often CPU intensive to run a complex
> canvas
> application in fullscreen.
>

Looking forward not-very-far, <canvas> will be scaled using the GPU for most
users, so this issue should go away. Or, you can put the canvas in the
middle of a blank page and make that fullscreen.

What are some real use-cases for capturing with the mouse up in
non-fullscreen windows? Do a significant number of users want to play
mouse-capturing games in non-fullscreen mode?

I agree an API to get mouse deltas is needed. I would suggest introducing a
completely separate API that lets applications monitor mouse deltas while
their window has focus, one that doesn't interact with normal mouse events
at all.

I don't think requiring a user click on a page to trigger capture is good
enough to prevent abuse. It's easy to get users to click on things in the
page.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Thursday, 10 February 2011 03:52:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT