- From: Gary Kacmarcik <notifications@github.com>
- Date: Tue, 06 Oct 2015 15:52:10 -0700
- To: w3c/uievents <uievents@noreply.github.com>
Received on Tuesday, 6 October 2015 22:53:04 UTC
Copied from W3C Bugzilla: https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259 ##### 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 --- Reply to this email directly or view it on GitHub: https://github.com/w3c/uievents/issues/17
Received on Tuesday, 6 October 2015 22:53:04 UTC