14457 2011-10-13 23:51:22 +0000 Add Element.dblclick. Apparently calling .click is better than synthesizing a click event using .createEvent, so there should be a .dblclick method aswell. 2011-10-24 23:07:42 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 58207 0 contributor 2011-10-13 23:51:22 +0000 Specification: http://www.w3.org/TR/html5/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: Add Element.dblclick. Apparently calling .click is better than synthesizing a click event using .createEvent, so there should be a .dblclick method aswell. Posted from: 94.223.193.24 User agent: Opera/9.80 (Windows NT 6.0; U; en) Presto/2.7.62 Version/11.01 58240 1 ian 2011-10-14 18:29:54 +0000 .click() is nothing like synthesizing a click event. It's how you actually cause the browser to act as if the user had clicked, which can't be done by synthesizing a click event. What's the use case for .dblclick()? 58788 2 ian 2011-10-24 23:07:42 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: see comment 1