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

Re: ISSUE-30: mousewheel event

From: Jim Ley <jim@jibbering.com>
Date: Mon, 27 Feb 2006 10:46:24 -0000
Message-ID: <033201c63b8b$22fd33f0$4aeefe51@Snufkin>
To: "Web APIs WG" <public-webapi@w3.org>

"Matthew Raymond" <mattraymond@earthlink.net>
>> MouseScroll is a bad name too, for mice with multiple scrollwheels, not 
>> all
>> of them generally scroll, nor is there always an inherent relationship
>> between wheels and scrolling, just a common one.
>   If the wheel doesn't scroll, why would you want it to trigger the
> event in the first place???

If it does scroll, why would I want it to?  they're equivalent statements 
really.  I want to catch events from input devices to override the default 
behaviour.  Whatever the default behaviour is is irrelevant.

>For instance, I have a button on the side of
> my mouse that's mapped by the mouse settings to the "middle button". My
> mouse doesn't actually have a middle button, because I have a scroll
> wheel there instead (although, technically that could be used as a
> button as well).

So on mousedown I would expect to get information that you mousedown'd with 
such a button, why would you not?

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

Of course it should, although you may want to configure your OS to hide it 
from the browser entirely.

> and the event in question occurs
> to the element under the pointer device, so it's clear that the first
> half of this event should be "mouse".

Is it clear that the wheel goes to the thing with mousefocus and not the 
focus?  I'm pretty sure when forms have focus in IE it goes with focus, so I 
would've thought it would always go with focus there.  That needs research.

Received on Monday, 27 February 2006 10:47:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:19 UTC