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

[Bug 11129] Remove forminput, formchange and related dispatch methods

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Jan 2011 13:07:06 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PhM8Q-0005hs-Df@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129

Olli Pettay <Olli.Pettay@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Olli.Pettay@gmail.com

--- Comment #6 from Olli Pettay <Olli.Pettay@gmail.com> 2011-01-24 13:07:05 UTC ---
One problem with forminput/formchange -like broadcasting events is that
what should happen when one of the targets is moved to another form
or even another document when some other target for the events is
handling the event. Well, perhaps nothing special shouldn't happen,
but it would be rather strange to get forminput when the element is in a
form which has never been used yet.

In fact, that sort of breaks the algorithm's step 3
"For each element in controls, in tree order, fire a simple event named event
name at the element."
Depending on how you read that, tree order should be checked either just
once before firing any events, or before each event.

-- 
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, 24 January 2011 13:07:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 January 2011 13:07:07 GMT