W3C home > Mailing lists > Public > public-pointer-events@w3.org > April to June 2013

Why doesn't touch-action affect pointerType mouse?

From: Daniel Freedman <dfreedm@google.com>
Date: Wed, 19 Jun 2013 16:12:39 -0700
Message-ID: <CAAUAVAid8S0yNmZ_nZDq2zeSjCKjRuTHqdBKEG8prTjMjGS+Uw@mail.gmail.com>
To: "public-pointer-events@w3.org" <public-pointer-events@w3.org>
I had a really good conversation with some of the other Polymer developers
today about how touch-action is supposed to work. They brought up a really
good point: *it's strange that touch-action only matters for touch input. *
In particular, it seems odd that the story of PointerEvents is that all the
input methods will behave the same, but mouse and pen could have more
fidelity than touch by default. By this I mean that it seems strange that
pointermove would occur for mouse and pen devices regardless of
touch-action value, but touch input needs to have touch-action: none set to
receive events.

Rather than attempt to make touches always emit pointermove, which would
clearly be problematic for scrolling, I suggest that we make pen and mouse
not emit pointermove by default, and only emit pointermove with the same
values of touch-action would emit pointermove for touch currently. While
this would mean more work for the developer, it would be less surprising
than receiving completely different sets of events from touch as from mouse
and pen.

Received on Wednesday, 19 June 2013 23:13:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:20:25 UTC