Re: Errata for Touch Events: clarify the "mouse events" also includes "click"

On Wed, Oct 29, 2014 at 9:52 PM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> Currently, the spec talks about "mouse events" but does not explicitly
> state that "click" in this context is also (wrongly, in my view, but hey
> ho) counted as a "mouse" event.
>
> This may require some awkward rewording. Perhaps the easiest way around
> this would be to add a note right at the start of "7. Interaction with
> Mouse Events" to specifically state something along the lines of
>
> "In the context of this specification, 'Mouse Events' also includes the
> <code>click</code> event"
>

That's fine with me.  We should probably also list the "contextmenu" event.

Otherwise, the change required may be a bit more drastic...something like:
>
> "7. Interaction with Mouse Events"
>
> change to
>
> "7. Interaction with Mouse and Click Events"
>
>
>
> "The user agent may dispatch both touch events and mouse events
> [DOM-LEVEL-2-EVENTS] in response to the same user input."
>
> change to
>
>  "In addition to touch events, the user agent may also dispatch mouse and
> click events [...] in response to the same user input, for compatibility
> with existing mouse based content"
> (so this would introduce the idea of "compatibility" events, which we
> could then use as shorthand to avoid the awkward "mouse and click events")
>
>
>
> "If the user agent dispatches both touch events and mouse events in
> response to a single user action, then the touchstart event type must be
> dispatched before any mouse event types for that action."
>
> change to
>
> "If the user agent dispatches both touch events and compatibility events
> in response to a single user action, then the touchstart event type must be
> dispatched before any compatibility event types for that action."
>
> (though note that this does not match reality in some browser, such as
> Android/Browser and some older Webkits, where mouseover and mousemove are
> usually sent *before* touchstart)
>
>
>
> " If the preventDefault method of touchstart or touchmove is called, the
> user agent should not dispatch any mouse event that would be a
> consequential result of the the prevented touch event."
>
> change to
>
> " If the preventDefault method of touchstart or touchmove is called, the
> user agent should not dispatch any compatibility event that would be a
> consequential result of the the prevented touch event."
>
>
>
> "...then the user agent may dispatch the mouse events to a different
> target than the touch events."
>
> change to
>
> "...then the user agent may dispatch the compatibility events to a
> different target than the touch events."
>
>
>
> "The default actions and ordering of any further touch and mouse events
> are implementation-defined, except as specified elsewhere."
>
> change to
>
> "The default actions and ordering of any further touch and compatibility
> events are implementation-defined, except as specified elsewhere."
>
> (side note: "elsewhere" where? do we mean elsewhere in this spec?
> elsewhere in some other spec? this last bit seems excessively wooly)
>
>
> And, if we do go for this proposed change, my previously proposed text for
> the non-normative event sequence should also match:
>
> "[...]no mouse or click events will be fired, and the resulting sequence
> of events would simply be"
>
> would need to be
>
> "[...] no compatibility event will be fired [...]"
>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>