- From: Gary Kacmarcik via GitHub <noreply@w3.org>
- Date: Mon, 12 Jan 2026 22:03:06 +0000
- To: public-pointer-events@w3.org
garykac has just created a new issue for https://github.com/w3c/pointerevents: == Expose ticks in wheel events == 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 Please view or discuss this issue at https://github.com/w3c/pointerevents/issues/585 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 January 2026 22:03:07 UTC