W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2010

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 24 Nov 2010 02:59:27 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PL5Zv-0008NZ-RK@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11129

--- Comment #1 from Rob Crowther <robertc@boogdesign.com> 2010-11-24 02:59:26 UTC ---
I'm not sure I get the 'increasing the size of the API' argument, can someone
expand on it?

To pick a some examples for comparison: Is it worth increasing the size of the
API to have valueAsNumber or valueAsDate when both can be easily worked around
by the developer if required?  Is it worth adding an output element when we
could just have a span and use innerHTML?

Why is this case less worthy than either of those two examples?

I like that an onforminput attribute can be added to the output element.  Even
if that isn't really best practice it's simple for beginners to grasp, and it
keeps all the logic for each output element in one place (and makes the output
element much easier to explain).

-- 
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 Wednesday, 24 November 2010 02:59:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 24 November 2010 02:59:32 GMT