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: Tue, 23 Aug 2011 12:04:00 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Qvpi4-0008FU-1h@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12230

--- Comment #20 from Olli Pettay <Olli.Pettay@gmail.com> 2011-08-23 12:03:58 UTC ---
(In reply to comment #19)
> 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 is what Gecko does: click() dispatches mouse click event and the default
action is to follow the link. That is how all the browsers work.

> That way calling .click() would follow the link, but calling .dispatchEvent
> would not.
Er, what?


> 
> 
> 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.
There are different kinds of events. Events which are notifications that
something has happened, like focus, and events which happen before default
handling happens, like click.

-- 
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, 23 August 2011 12:04:01 UTC

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