This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24784 - ACTION-69: Create a proposal re informative note re pointerevent and touchevent compatibility
Summary: ACTION-69: Create a proposal re informative note re pointerevent and toucheve...
Status: RESOLVED FIXED
Alias: None
Product: PointerEventsWG
Classification: Unclassified
Component: Pointer Events specification (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Jacob Rossi [MSFT]
QA Contact: Pointer Events Bugzilla list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-24 13:58 UTC by Patrick H. Lauke
Modified: 2014-03-05 18:25 UTC (History)
1 user (show)

See Also:


Attachments

Description Patrick H. Lauke 2014-02-24 13:58:58 UTC
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?]"
Comment 1 Jacob Rossi [MSFT] 2014-03-04 02:10:15 UTC
This is a lot more specific and verbose than what I think we discussed last week on the 2/25 call. The topic of the relationship between Touch Events and Pointer Events is the explicit scope of the Touch Events Community Group and the specifics of which have yet to really have been sorted out by that group.

Therefore, the best approach I believe is to just add a non-normative reference to the work of that group (directly prior to the sentence that begins "For compatibility with content written to mouse-specific events"):

"For information on the relationship between Pointer Events and Touch Events, see the Touch Events Community Group."

and link "Touch Events Community Group" to the TECG wiki for more detailed information.

Doing this avoids baking in any premature descriptions of the relationship and makes the TECG wiki an extensibility point for nailing down a crisp description of that relationship.
Comment 2 Patrick H. Lauke 2014-03-04 08:22:18 UTC
Jacob, you're right, this is indeed more verbose and it's best served on the CG wiki...I just haven't gotten around to doing that (but agreed on the call 2/25 that that would be best course of action).
Comment 3 Patrick H. Lauke 2014-03-04 08:34:27 UTC
Expanding your counter-proposed text just slightly, for more context, I'd suggest the following NOTE (and I'd put it *after* the "For compatibility with content written to mouse-specific events [...] other than a mouse." sentence, so as not to break up the logical flow of the previous sentence too much).

"NOTE:

This document does not provide any advice on the expected behavior of user agents that intend to support both Pointer Events and <a href="http://www.w3.org/TR/touch-events/">Touch Events</a>. For more information on the relationship between these two specifications, see the <a href="http://www.w3.org/community/touchevents/">Touch Events Community Group</a>."
Comment 4 Jacob Rossi [MSFT] 2014-03-05 18:25:07 UTC
Changed as proposed by PL below and discussed on 3/4 meeting:

https://dvcs.w3.org/hg/pointerevents/rev/ac1f10dc03eb