- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Thu, 16 Jun 2011 08:54:39 -0400
- To: Daniel Glazman <daniel.glazman@disruptive-innovations.com>, www-dom <www-dom@w3.org>
Daniel - as one of the moderators of www-dom, please note some members find your tone below unacceptable. Also, I am not aware of a public reference for the e-mail you quoted from Mounir Lamouri (please provide a link to Mounir's e-mail). All - this is a reminder that all e-mails on this list are expected to be respectful and professional. Please see the following for more information about the etiquette and usage of this list: http://www.w3.org/2008/webapps/wiki/WorkMode#Mail_List_Policy.2C_Usage.2C_Etiquette.2C_etc. -Regards, Art Barstow -------- Original Message -------- Subject: Re: Fwd: comment on DOM 3 Events LC #2 on WebApps WG's request Resent-Date: Thu, 16 Jun 2011 10:37:46 +0000 Resent-From: <www-dom@w3.org> Date: Thu, 16 Jun 2011 12:37:07 +0200 From: ext Daniel Glazman <daniel.glazman@disruptive-innovations.com> To: <www-dom@w3.org> Le 16/06/11 12:17, Mounir Lamouri a écrit : > Generally speaking, I think it's too soon to add these kind of events: > HTML5 Forms implementations are young and I still haven't see one > website using it. Really a bad argument. Our specs are supposed to pave the future, not stabilize what's already here. > In addition, I do not think it would be a good idea to have an event > being sent when an element becomes valid or invalid: I do not see any > good use case (wrt UX) that wouldn't work with the input or change > events. What use cases do you have in mind? That's a joke I presume ??? A form willing to cancel the transaction after three failed attempts to enter something valid ? A form willing to emit a XHR if a field goes off-range or invalid ? There are _tons_ of use case. > Furthermore, for in-range and out-of-range, I do not believe a good > implementation should allow the user to enter an out of range value so > such an event might be useless. Even if, I don't see how invalid/valid > events wouldn't fulfill the hypothetical use cases of those two. A "good" implementation ?!?!? Wow. Suppose you have a form with an email field. That field's value is populated BY SCRIPT just because you have a password helper. Oh, your bad, the data in your passwd helper is wrong, you mistyped your email, forgot a period. Dang, the form field is invalid. Mounir, this is not an ideal world, the browser is not the only user-side component of the web, and the user is not the only one filling up form fields. Wake up, please. </Daniel>
Received on Thursday, 16 June 2011 12:55:06 UTC