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

[Bug 24921] New: ACTION-88: Clarification of "Default Action" for pointerdown wrt compat mouse events

From: <bugzilla@jessica.w3.org>
Date: Tue, 04 Mar 2014 20:32:22 +0000
To: public-pointer-events@w3.org
Message-ID: <bug-24921-5978@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24921

            Bug ID: 24921
           Summary: ACTION-88: Clarification of "Default Action" for
                    pointerdown wrt compat mouse events
           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

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 4 March 2014 20:32:23 UTC

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