- From: <bugzilla@jessica.w3.org>
- Date: Mon, 16 Sep 2013 21:55:51 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23259
Bug ID: 23259
Summary: Expose ticks in wheel events
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: DOM3 Events
Assignee: travil@microsoft.com
Reporter: garykac@google.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
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?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 16 September 2013 21:55:53 UTC