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

Re: Proposal for mousewheel events

From: Maciej Stachowiak <mjs@apple.com>
Date: Mon, 27 Mar 2006 17:33:43 -0800
Message-Id: <00227FBE-11A7-4D29-B5A0-5225905016D2@apple.com>
Cc: Anne van Kesteren <annevk@opera.com>, "Web APIs WG (public)" <public-webapi@w3.org>
To: Ian Hickson <ian@hixie.ch>

On Mar 27, 2006, at 5:30 PM, Ian Hickson wrote:

> On Mon, 27 Mar 2006, Anne van Kesteren wrote:
>> I'm not sure if the interface given in
>> http://www.w3.org/mid/71BB13FE-115D-425F-9045-1BA16629D247@apple.com
>> makes sense. What basically bugs is me that we would have two  
>> almost the
>> same interfaces except for one attribute. If we only need .wheelDelta
>> I'd suggest we consider options (a), (b) and (d) from ISSUE-55 unless
>> someone has good reasons to go with a new interface instead --
>> duplicating most of what MouseEvent currently says.
> Why not just do:
>    interface MouseWheelEvent: MouseEvent {
>      readonly attribute long wheelDelta;
>    }
> ...where |wheelDelta| is a multiple of 120 (positive means rotated  
> away
> from user or to the right, negative means rotated towards user or  
> to the
> left), and we set |detail| to wheelDelta divided by 120? Backwards
> compatible with IE and Safari (and thus with existing content), and
> sensible at the same time.
> (Issue: In an RTL environment, should it be right/left as well or
> left/right instead? I suggest raising this with i18n.)

I think the only issue with this might be whether it is possible to  
provide a correct value for the "button" attribute. I'm not sure if  
platform wheel events provide that.

Received on Tuesday, 28 March 2006 01:34:11 UTC

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