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: Tue, 08 Mar 2011 18:16:42 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Px1Sc-0000aI-Cd@jessica.w3.org>

--- Comment #13 from Jacob Rossi [MSFT] <jrossi@microsoft.com> 2011-03-08 18:16:41 UTC ---
My understanding is that certain ATs use synthetic click events to activate
elements. Compat w.r.t. accessibility is a good reason to have this exception.
The fact that Gecko does not do this is not enough evidence to remove this

D3E says nothing of form submission or how link navigation occurs (contrary to
what you suggest). In fact, the submit event isn't even in D3E:

"The change, submit, and reset events were removed [from D3E], since they were
specific to HTML forms, and are specified in HTML5."

While it does cover the existance of UI events, it simply notes that such
events will have UA specific default actions (form submission and link
navigation are non-normative examples).

The rule of thumb that untrusted events do not invoke UA default actions is
something intrinsic to events and thus does belong in D3E. 

The exception for click is purely an acknowledgement that this behavior exists
and is used today. If you'd like a more comprehensive explanation, look back at
the www-dom threads about why DOMActivate isn't typically used by ATs.

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 Tuesday, 8 March 2011 18:16:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:06 UTC