W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 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, 22 Aug 2011 20:24:51 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qvb3D-0007CA-Mf@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12230

--- Comment #19 from Jonas Sicking <jonas@sicking.cc> 2011-08-22 20:24:49 UTC ---
I still think that events should be fired in response to actions. Firing events
isn't what causes actions.

It would have been a much better and consistent solution for Gecko to make
<a>.click() dispatch an untrusted event, but have the default action for that
event be to follow the link.

That way calling .click() would follow the link, but calling .dispatchEvent
would not.


For the vast majority of events we can't make calling .dispatchEvent execute
the default action as .dispatchEvent simply doesn't provide enough data. Hence
we should be consistent and never make .dispatchEvent execute the default
action.

-- 
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, 22 August 2011 20:24:52 UTC

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