Hello WG, During our first DOM 3 Events telcon I was given an action to summarize any outstanding dblclick and to bring them up to the group for closure.
>From the tracker issues database there are two unopened issues regarding >dblclick: ISSUE-81: What should detail be for dblclick events? http://www.w3.org/2005/06/tracker/webapi/issues/81 and ISSUE-82: should Anne's proposed even click count rule for dblclick be a normative requirement? http://www.w3.org/2005/06/tracker/webapi/issues/82 Regarding ISSUE-81 - the e-mail threads ended with two options - either making dblclick.detail == click.detail or making it a constant. The current WD has both dblclick.detail and click.detail equal to the "current click count" [1]. This seems consistent with the e-mail thread regarding the issue. Please provide feedback before our next telcon on February 20th, as this will be discussed and resolved at that time. Regarding ISSUE-82, the e-mail discussion that followed discussed a number of solutions: 1. adding "current click count % 2 == 0 " as a normative requirement 2. adding "current click count == 2" as a normative requirement 3. adding text stating that current click count is the number of consecutive clicks, the notion of which depends on the environment configuration The current draft of the spec has the wording from option 3[1]. Again, this seems consistent with the e-mail thread regarding the issue. Please provide feedback before our next telcon on February 20th, as this will be discussed and resolved at that time. All the best, Andrew [1] http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-eventgroupings-mouseevents Andrew Emmons Architect and Manager, SVG Technologies Co-Chair, W3C SVG Working Group Open Text Corporation, BitFlash Division 515 Legget Drive, Suite 300 Ottawa ON K2K 3G4 Tel: 613.599.9335 ext.3248 Fax: 613.599.9177 Web: www.bitflash.com www.opentext.com
