W3C home > Mailing lists > Public > public-webapi@w3.org > February 2006

Re: ISSUE-30: mousewheel event

From: Matthew Raymond <mattraymond@earthlink.net>
Date: Tue, 28 Feb 2006 17:27:53 -0500
Message-ID: <4404CE69.10307@earthlink.net>
To: Anne van Kesteren <annevk@opera.com>
CC: "Web APIs WG (public)" <public-webapi@w3.org>

Anne van Kesteren wrote:
> On Sun, 26 Feb 2006 06:55:48 +0100, Matthew Raymond  
> <mattraymond@earthlink.net> wrote:
>> If the wheel doesn't scroll, why would you want it to trigger the
>> event in the first place???
> 
> So you can use it for zooming instead. (If there is a scrollbar you could  
> do this by canceling the event...)

   I don't get it. While you may use the mouse wheel for the purpose of
zooming, the event it should trigger should be something like
"mousezoom". You're essentially saying that W3C specs can require a
certain type of physical device be used for a specific type of input. As
games have shown us, you can configure things like keyboards, mice,
joysticks, et cetera, to trigger specific input events. If the software
then overrides such configurations, the configurations are useless.

>> If I
>> configure my mouse wheel to be an "Undo" button, it should trigger a
>> "mousewheel"-type event in the first place.
> 
> Is this what actually happens?

   Well, I meant to say "shouldn't", but yeah, I can pretty much
configure my mouse buttons to do what ever I want, short of running a
specific application, and it comes close because I can configure it to
open the Windows run dialog.
Received on Tuesday, 28 February 2006 22:28:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT