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

Re: ACTION-91: mousewheel event

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 13 Mar 2006 17:49:47 +0100
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <m98b12lufr6tqov5j6cp855jpm5u9qs9or@hive.bjoern.hoehrmann.de>

* Anne van Kesteren wrote:
>Here is some text for a mousewheel event per our latest telcon. We decided  
>to postpone discussing multiple directions or multiple input devices for  
>now (ISSUE-33). It is unclear to me whether my action included drafting up  
>the interface or not so I left that out for now...
>
>  mousewheel
>    The mousewheel event MUST be dispatched on the currently
>    focused object when the user uses his mouse wheel or uses a
>    device that achieves similar effects as mouse wheels
>    according to platform conventions or environment
>    configuration.

The event is dispatched to the primary subject of user interaction
relative to the input device. This may be the focused event target,
it may also be some other component of the user interface. Which
event target exactly depends on platform conventions. For example,
if a <select> is active, rotating the wheel is likely to scroll the
list, regardless of where the cursor is; if, on the other hand, a
simple text <input> is active, the event is dispatched to the event
target under the cursor.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 13 March 2006 16:49:48 GMT

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