W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2014

Re: [DOM3Events] Identifying mouse events derived from touch events

From: Rick Byers <rbyers@chromium.org>
Date: Tue, 2 Sep 2014 17:33:45 -0400
Message-ID: <CAFUtAY-jpAs77eSXAaY3ydJSV7SZTbczgmLeBJhFj8icuGEg8w@mail.gmail.com>
To: Robert Kroeger <rjkroege@google.com>
Cc: "www-dom@w3.org" <www-dom@w3.org>, input-dev <input-dev@chromium.org>
On Tue, Sep 2, 2014 at 5:17 PM, Robert Kroeger <rjkroege@google.com> wrote:

>
> On Tue, Sep 2, 2014 at 12:19 PM, Rick Byers <rbyers@chromium.org> wrote:
>
>> On Tue, Sep 2, 2014 at 3:01 PM, Robert Kroeger <rjkroege@google.com>
>> wrote:
>>
>>>
>>> On Wed, Aug 27, 2014 at 7:26 AM, Rick Byers <rbyers@chromium.org> wrote:
>>>
>>>> Hi,
>>>> Web developers have long struggled to reliably identify which mouse
>>>> events are actually derived from touch events.  Sites need to know this to
>>>> avoid double handling (eg. on both a touchend and click event), and have
>>>> often just ignored all mouse events on a browser that supports touch events
>>>> - seriously breaking functionality on devices with both a mouse and
>>>> touchscreen.
>>>>
>>>> We (blink team) have tried for over a year to address this problem
>>>> through evangelism (eg. encouraging
>>>> <http://www.html5rocks.com/en/mobile/touchandmouse/> calling
>>>> <https://www.youtube.com/watch?v=DujfpXOKUp8> preventDefault on
>>>> handled touch events to suppress the generated mouse events).  The
>>>> situation has improved, but it's still a major problem (eg. it's the reason
>>>> we haven't yet been able to rationalize Chrome's support for
>>>> TouchEvents
>>>> <https://code.google.com/p/chromium/issues/detail?id=392584> across
>>>> devices, and the reason the IE team says
>>>> <http://lists.w3.org/Archives/Public/public-touchevents/2014Jul/0025.html> they
>>>> implement touch events only on phones, not laptops).
>>>>
>>>> I recognize now that avoiding
>>>> <https://code.google.com/p/chromium/issues/detail?id=115475#c13>
>>>> adding a new simple API for this was a *big mistake*.  There are
>>>> legitimate reasons why the available workarounds are inadequate. For
>>>> example, you may want to suppress/ignore mouse events without disabling
>>>> browser behavior like focusing, activating links, etc.  Or some listeners
>>>> may want to ignore certain mouse events whose handling is redundant with
>>>> that for touch events without affecting other listeners (perhaps in other
>>>> components written by other developers).
>>>>
>>>> After considering a number of more general alternatives
>>>> <https://docs.google.com/a/chromium.org/document/d/1-ZUtS3knhJP4RbWC74fUZbNp6cbytG6Wen7hewdCtdo/edit#>,
>>>> I'd like to propose a very simple and targeted *addition to
>>>> MouseEvent:* *a boolean 'derivedFromTouchEvent' property*.  Note that
>>>> this intentionally says the event represents input that was already
>>>> reported via some other event, NOT that the event represents input from a
>>>> touchscreen device (eg. browsers on Android send touch events for mouse and
>>>> stylus, not just touch input).
>>>>
>>>
>>> I think this is a good choice for letting a site determine if the mouse
>>> events are derived from touch input.
>>>
>>> Is it worth considering one possible extension: given a derived event,
>>> is it worth letting the UA specify to the site what was the origin of the
>>> event?
>>>
>>
>> Thanks Rob.  What sort of "origin"s were you imagining here?  Do you mean
>> just other possibilities than just "from touch" (eg. 'click' events can be
>> 'derived' from keyboard input)?  Or do you mean for the derived-from-touch
>> case, more details on the original action like "derived from a tap gesture"?
>>
>
> I was trying to anticipate future UAs deriving standard mouse / click
> events from gestures coming from still unusual devices like the Thalmic
> labs arm band. The site might want to take special action in such a context.
>

I'd like to see that too (eg. I could see an argument for pushing the
"pointerType" property from PointerEvent down to MouseEvent or even
UIEvent).  However I believe the question of "what device did this come
from" and "what events is this redundant with" are orthogonal questions
that should be addressed through orthogonal APIs. They're similar, but if
we conflate the two we're likely to cause a world of confusion.  Eg. Chrome
and Firefox on Android send touch events for mouse input - mouse events
generated in that scenario should be marked "derivedFromTouchEvent" but NOT
pointerType="touch".  Conversely, desktop IE fires mouse events for touch,
but they don't send touch events, so those should be pointerType="touch"
but NOT "derivedFromTouchEvent".

Anyway If we also want to discuss a "device source" API here for
MouseEvent, that's great too!  But we need a separate API for that which I
don't think would directly affect the design of the API I'm proposing here.

 With this we could encourage sites to trivially transform this common
>>>> broken pattern:
>>>>
>>>> if (‘ontouchstart’ in window)
>>>>   document.addEventListener(‘touchstart’, doStuff);
>>>> else
>>>>   document.addEventListener(‘mousedown’, doStuff);
>>>>
>>>>
>>>> Into this:
>>>>
>>>> document.addEventListener(‘touchstart’, doStuff);
>>>> document.addEventListener(‘mousedown’, function(e) {
>>>> if (!e.derivedFromTouchEvent) doStuff(e);
>>>> });
>>>>
>>>>
>>>> This new API can be trivially polyfilled on browsers (like Safari)
>>>> which never support mouse and touch input at the same time with just:
>>>>
>>>> if (!('derivedFromTouchEvent' in MouseEvent.prototype))
>>>>
>>>>     MouseEvent.prototype.derivedFromTouchEvent = ‘ontouchstart’ in
>>>> window;
>>>>
>>>>
>>>> See this document
>>>> <https://docs.google.com/a/chromium.org/document/d/1-ZUtS3knhJP4RbWC74fUZbNp6cbytG6Wen7hewdCtdo/edit#>
>>>> for more details and other alternative proposals.
>>>>
>>>> Thanks,
>>>>    Rick
>>>>
>>>
>>>
>>
>
Received on Tuesday, 2 September 2014 21:34:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:23 UTC