W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2011

[Bug 12230] From this algorithm it does not seem to follow that dispatching a synthetic non-canceled submit event at a form causes it to be submitted. Yet that is what browsers implement. So that forms have a default handler for submit events should probably be split

From: <bugzilla@jessica.w3.org>
Date: Mon, 07 Mar 2011 18:13:45 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PwewD-0005d8-VS@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12230

Jacob Rossi [MSFT] <jrossi@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jrossi@microsoft.com

--- Comment #7 from Jacob Rossi [MSFT] <jrossi@microsoft.com> 2011-03-07 18:13:44 UTC ---
DOM L3 Events states that "Most untrusted events should not trigger default
actions, with the exception of click..."[1].

IE9 and Webkit match this behavior:

* synthetic click events on links cause navigation
* synthetic submit events on forms do not cause form submission

The HTML5 form submission algorithm matches D3E, IE9, and Webkit. 

In general, I think D3E is right that untrusted events should not induce
default actions. The exception for click is mostly historical (because click is
often used as an activation event).

I don't think this change is advised.

[1]
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#trusted-events

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 7 March 2011 18:13:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 March 2011 18:13:51 GMT