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:26:39 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1Pwf8h-0006Eg-W7@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12230

--- Comment #8 from Anne <annevk@opera.com> 2011-03-07 18:26:39 UTC ---
So a) that is not really saying anything at all in a normative way and b) the
way the events model works is that the code that dispatches the event also
invokes the default handler. Otherwise why would dispatchEvent() have a return
value?

But here the code that dispatches the event (author-provided code) is
completely disjoint from the code with the default handler (browser-provided
code).

I.e. from the events model you expect code to work like this:

if(target.dispatchEvent(ev))
  defaultHandler()

-- 
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:26:41 GMT

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