W3C home > Mailing lists > Public > public-pointer-events@w3.org > January to March 2014

[Bug 24784] New: ACTION-69: Create a proposal re informative note re pointerevent and touchevent compatibility

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Feb 2014 13:58:58 +0000
To: public-pointer-events@w3.org
Message-ID: <bug-24784-5978@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24784

            Bug ID: 24784
           Summary: ACTION-69: Create a proposal re informative note re
                    pointerevent and touchevent compatibility
           Product: PointerEventsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Pointer Events specification
          Assignee: jrossi@microsoft.com
          Reporter: redux@splintered.co.uk
        QA Contact: public-pointer-events-bugzilla@w3.org
                CC: public-pointer-events@w3.org

My first attempt at explicitly saying why the PE spec does not try and also
explain how UAs can handle both touch and pointer events. Probably too
wordy...feel free to hack it into shape.

This would be an expansion of the last paragraph of the current introduction:



"While Pointer Events are sourced from a variety of input devices, they are not
defined as being generated from some other set of device-specific events. While
possible and encouraged for compatibility, this spec does not require other
device-specific events be supported (e.g. mouse events, touch events, etc.). A
user agent could support pointer events without supporting any other device
events. For compatibility with content written to mouse-specific events, this
specification does provide an optional section describing how to generate
compatibility mouse events based on pointer input from devices other than a
mouse."



Split up slightly and expanded, I'd propose this (still just as main text for
the intro, not as a separately highlighted NOTE or anything).



"While Pointer Events are sourced from a variety of input devices, they are not
defined as being generated from some other set of device-specific events. While
possible and encouraged for compatibility, this spec does not require other
device-specific events be supported (e.g. mouse events, touch events, etc.).

A user agent could support pointer events without supporting any other device
events. Conversely, a user agent could support other device-specific events in
addition to pointer events.

For compatibility with content written to mouse-specific events, this
specification does provide an optional section describing how to generate
compatibility mouse events based on pointer input from devices other than a
mouse.

This specification does not provide any advice on the expected behavior of user
agents that intend to support both pointer events and touch events [link to
http://www.w3.org/TR/touch-events/]. Although in the case of touch input there
are some superficial similarities between pointer events and touch events,
their model - implicit versus explicit capture, the <code>TouchList</code>
objects, the way in which compatibility mouse events are fired and suppressed,
the fact that touch events consider <code>click</code> to be a compatibility
event which can be suppressed - is fundamentally different, meaning that user
agents will have to employ complex strategies and decide on which model to
prioritise when attempting to handle both event types. [should/can we point to
the W3C Touch Events CG here?]"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 24 February 2014 13:59:00 UTC

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