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 24921 - ACTION-88: Clarification of "Default Action" for pointerdown wrt compat mouse events
Summary: ACTION-88: Clarification of "Default Action" for pointerdown wrt compat mouse...
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-03-04 20:32 UTC by Patrick H. Lauke
Modified: 2014-03-24 16:59 UTC (History)
1 user (show)

See Also:


Attachments

Description Patrick H. Lauke 2014-03-04 20:32:22 UTC
Currently, the default action for pointerdown reads:

"Varies: when the pointer is primary, all default actions of the mousedown event plus firing of compatibility mouse events"

Although now I understand what is meant based on clarification given here http://lists.w3.org/Archives/Public/public-pointer-events/2014JanMar/0152.html the wording may still be confusing, at it still - on first skimming the table - reads too much like ALL compatibility mouse events are ONLY fired after pointerdown, and conversely that cancelling pointerdown would stop ALL compat events from being generated.

I'd propose a slight rewording that hopefully captures the reality (that yes, pointerdown does in fact "control" SOME compat events, and that cancelling it conversely does stop SOME of them) a bit better.

It's easier, in my view, to talk about the opposite of the default action - i.e. what happens when the event is cancelled - so my preferred wording would be:


"Varies: when the pointer is primary, all default actions of the mousedown event. Cancelling this event also sets the PREVENT MOUSE EVENT flag for this pointerType, which prevents subsequent firing of certain compatibility mouse events."


As ever, a bit verbose, and the fact that I'm describing the opposite (what happens when the default action is prevented, rather than what the default action is) may not be ideal...but I'm struggling to find a way to word the exact opposite in a sufficiently accurate way.
Comment 1 Jacob Rossi [MSFT] 2014-03-11 05:25:18 UTC
I'm fine with making this change.  It's more specific as to what exactly happens and plugs in better to the algorithm used elsewhere in the spec.
Comment 2 Jacob Rossi [MSFT] 2014-03-24 16:59:33 UTC
Spec updated per resolution
https://dvcs.w3.org/hg/pointerevents/rev/053b14a9873e