W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2008

Re: Wheel events

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Thu, 19 Jun 2008 00:05:00 +0300
Message-ID: <4859787C.109@helsinki.fi>
To: "public-webapps@w3.org" <public-webapps@w3.org>



Olli Pettay wrote:
> 
> Hi all,
> 
...

> So there are (at least) 5 options
> 1. only pixel delta
> - Web app can't know what delta value means a "line scroll"
> 2. events with both line and pixel scroll information (maybe also page
> scroll etc?)
> - Web apps would get all the needed information in one event,
> but the event interface would probably look pretty ugly
> 3. separate events for pixel scrolls and line scrolls
> - Web app can't know whether user did one or two gestures
> 4. linked events; if the native event contains both line and pixel
> data, dispatch one event for line delta and one for pixel data
> but add some attribute to the event interface which links these
> events together, something like
> readonly attribute WheelEvent relatedEvent;
> or
> readonly attribute WheelEventList relatedEvents;
> 5. no pixel scrolling at all
> - causes http://mozilla.pettay.fi/moztests/pixelscrolling.mov
> 
Or 6.
Perhaps the type of deltaX/Y/Z  shouldn't be just long.
It could an array of longs or an array of wheelrollvalues (whatever 
those are).

Something where event.deltaX[0] would be the most significant
and event.deltaX[event.deltaX.length] the least significant;
in practise event.deltaX[0] could be the line scrolling part,
event.deltaX[1] the pixel scrolling

An array of values would be easy to extend.

> 
> 
> -Olli
> 
> 
Received on Wednesday, 18 June 2008 21:08:03 GMT

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