Bug 65215 - dispatchEvent should not trigger default actions (for synthetic events)
Summary: dispatchEvent should not trigger default actions (for synthetic events)
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: DOM (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 27880
Blocks:
  Show dependency tree / graph
 
Reported: 2011-07-26 16:01 PDT by Darin Fisher (:fishd, Google)
Modified: 2011-07-26 16:33 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Fisher (:fishd, Google) 2011-07-26 16:01:34 PDT 
dispatchEvent should not trigger default actions

http://www.whatwg.org/specs/web-apps/current-work/#interactive-content

Note this tid-bit:
"The above doesn't happen for arbitrary synthetic events dispatched by author script. However, the click() method can be used to make it happen programmatically."

This came up in the context of https://bugs.webkit.org/show_bug.cgi?id=64580.
Comment 1 Darin Fisher (:fishd, Google) 2011-07-26 16:23:20 PDT 
I suspect that we should fix https://bugs.webkit.org/show_bug.cgi?id=27880 along with this.  It is important that people have a programmatic way to "click" on an element if synthetic "click" events are going to be neutered.