This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23259 - Expose ticks in wheel events
Summary: Expose ticks in wheel events
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - UI Events (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-16 21:55 UTC by Gary Kacmarcik
Modified: 2015-10-06 22:52 UTC (History)
3 users (show)

See Also:


Attachments

Description Gary Kacmarcik 2013-09-16 21:55:51 UTC
We should consider adding |ticks| to the wheel event.

There are many UX use cases where ticks are more appropriate than pixels, especially considering that pixel values vary from system-to-system (and can vary based on user preferences).

An example of when ticks are more appropriate is with a "digit-selector", a menu or a drop-down list. In each of these cases, a single tick should select the next element regardless of how many "pixels" are reported.

Issues:
What ticks value should be used for input devices that fake scrollwheel events (like a touchpad)?  Options are to simply use 0 ticks for these devices, come up with a method for generating fake ticks.

Do we need x, y and z ticks?
Comment 1 Gary Kacmarcik 2013-10-23 13:53:26 UTC
Moving to UI Events
Comment 2 Gary Kacmarcik 2015-10-06 22:52:23 UTC
Now tracking as: https://github.com/w3c/uievents/issues/17