- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Tue, 10 Dec 2013 16:46:18 +0000
- To: Rick Byers <rbyers@google.com>, "public-pointer-events@w3.org" <public-pointer-events@w3.org>
On a related topic, I find the "5.2.1 List of Pointer Events" table https://dvcs.w3.org/hg/pointerevents/raw-file/tip/pointerEvents.html#list-of-pointer-events and in particular the Default Action column slightly confusing. As established in the "Compatibility Mapping" section, pointer and mouse events are fired in an interleaved way (for primary pointer, unless cancelled for some). For this reason, the "plus dispatch of compatibility mouse events" which only appears in the default actions for pointerdown seems confusing. Now, this could be in part due to language - in UK, "dispatch" is generally used to mean "sending", while I know that in US it's more commonly used for its other meaning of "prevent/kill/stop" (I seem to remember Rick using it in that way in a few early exchanges we had). However, speaking with Jacob Rossi, it seems that it WAS actually meant to mean "send"... in which case I'm still confused why it would only be the default action for pointerdown, if in fact all other pointer events also fire their compatibility mouse events right away (again, if primary and not cancelled). Some clarification here would be welcome (or at least remove the "plus dispatch..." part entirely? P -- Patrick H. Lauke ______________________________________________________________ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com | http://flickr.com/photos/redux/ ______________________________________________________________ twitter: @patrick_h_lauke | skype: patrick_h_lauke ______________________________________________________________
Received on Tuesday, 10 December 2013 16:46:39 UTC