22072 2013-05-17 16:09:29 +0000 "current click count" deserves its own attribute 2013-06-19 00:08:25 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified PC All RESOLVED WONTFIX P2 normal --- 1 garykac travil annevk bugs mike www-dom public-webapps-bugzilla oldest_to_newest 87803 0 garykac 2013-05-17 16:09:29 +0000 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? 87804 1 annevk 2013-05-17 16:24:38 +0000 It has been .details since forever I think. Not sure why'd change that. 87822 2 bugs 2013-05-17 17:51:38 +0000 Yeah, .detail has been used for that for ages. In theory we could add another property but not sure why. 87864 3 garykac 2013-05-18 01:27:54 +0000 Having a named property for a specific purpose is better than storing data in a generic catch-all 'data' (or 'detail' in this case) attribute. Code that references something like 'event.clickCount' is self-documenting whereas with 'event.detail' you have to think about what is stored there for the particular event you're looking at. So, a proper attribute name is clearly better, but perhaps it's too late to update this.