W3C home > Mailing lists > Public > public-webevents@w3.org > July to September 2012

Touch Events version 2 - Requesting evaluation of feasibility to exploit touch pressure values to enable equivalent of mouse hover events on mobile touch devices

From: Richard Creamer <2to32minus1@gmail.com>
Date: Fri, 20 Jul 2012 20:17:32 -0700
Message-ID: <CAJ0kJcKkUwDTq5dShHZPcpbuHKFkkVbv0a9ijeWZpM8dVxcRPg@mail.gmail.com>
To: "public-webevents@w3.org" <public-webevents@w3.org>
Dear Editors:

The Touch Events version 2 document is, to me, unclear as to whether the
equivalent of mouse over/move/hover events are intended to be
included/supported.

 I would very much like to see touch screen devices support the equivalent
of a mouse over/move/hover event. This feature enables much more dynamic
UIs, and would go a long way towards eliminating one of the few remaining
advantages that mouse-equipped desktops and touch pad-equipped laptops have
over touch devices.  (I would like to point out that touch pads on laptops
support these events.)

 I had hoped that the touch event pressure value range [0, 1] was being
fully utilized so that I could emulate this type of event in my own
applications, but upon writing a simple Android test app for my phone,
discovered that all pressure values were primarily compressed into the
range of approximately [0.15 - 0.30] representing the lightest to the
strongest touch events I could create. (I should mention that I have a
high-end aftermarket screen protector on my phone which conceivably might
be compressing the pressure values.)

 If the pressure value's dynamic range were more fully utilized, it may be
feasible to reserve a standardized touch event pressure range to represent
the equivalent of a mouse over/move/hover event, while higher-pressure
touch events could initiate the already-implemented touch events.

 My purpose in submitting this is to suggest that this possibility be
considered. Perhaps hardware or platform vendors could calibrate their
pressure readout values to be more evenly distributed throughout the [0, 1]
range such that my suggestion can be adopted.

Thank you for your consideration.

 Richard Creamer
Individual
Received on Sunday, 22 July 2012 14:56:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 July 2012 14:56:59 GMT