23259 2013-09-16 21:55:51 +0000 Expose ticks in wheel events 2015-10-06 22:52:23 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - UI Events unspecified PC All RESOLVED MOVED P2 normal --- 1 garykac garykac mike public-webapps www-dom public-webapps-bugzilla oldest_to_newest 93458 0 garykac 2013-09-16 21:55:51 +0000 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? 95191 1 garykac 2013-10-23 13:53:26 +0000 Moving to UI Events 123552 2 garykac 2015-10-06 22:52:23 +0000 Now tracking as: https://github.com/w3c/uievents/issues/17