W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

[Bug 22072] New: "current click count" deserves its own attribute

From: <bugzilla@jessica.w3.org>
Date: Fri, 17 May 2013 16:09:29 +0000
To: www-dom@w3.org
Message-ID: <bug-22072-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22072

            Bug ID: 22072
           Summary: "current click count" deserves its own attribute
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: garykac@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

In 5.2.3 Mouse Event Types:
http://www.w3.org/TR/DOM-Level-3-Events/#events-mouseevents

The last paragraph of this section states:

"Implementations must maintain the current click count when generating mouse
events. This must be a non-negative integer indicating the number of
consecutive clicks of a pointing device button within a specific time. The
delay after which the count resets is specific to the environment
configuration."

Later on, the spec indicates that this should be stored in UIEvent.detail.

If nothing else, there should be more information in 5.2.3 about where/how the
click count is stored/used.

But why isn't this stored in a proper attribute rather than stuffed away in a
generic 'detail' attribute?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 17 May 2013 16:09:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:20 UTC