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 14:38:10 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PhNYY-0002dR-So@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129

--- Comment #7 from Rob Crowther <robertc@boogdesign.com> 2011-01-24 14:38:10 UTC ---
> all those can be trivially handled without these additional events

What does your definition of 'trivially handled' encompass?  Here's the amount
of JavaScript required in the spec examples purely in terms of character counts
(not including spaces):

calculator: 67 characters
password validity: 37 characters
car price: 15 characters

Plus, slightly more meta, understanding of event bubbling required: false.

With your examples:

calculator: 200 characters
password validity: 185 characters
car price: 116 characters

Understanding event bubbling required: true.

I don't agree that you can so easily characterize a minimum of 300% more code
and the requirement to understand event bubbling as trivial.

> I do think forminput and formchange are not needed

As I previously asked, why is this not needed, but valueAsNumber is?

-- 
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 14:38:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 24 January 2011 14:38:19 GMT