Bug 65215
| Summary: | dispatchEvent should not trigger default actions (for synthetic events) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Darin Fisher (:fishd, Google) <fishd> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, ian |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 27880 | ||
| Bug Blocks: | |||
Darin Fisher (:fishd, Google)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Darin Fisher (:fishd, Google)
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.