- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 29 Sep 2011 09:25:48 -0700
On Thu, Sep 29, 2011 at 12:32 AM, Matias <matiasnu at gmail.com> wrote: > > On 29 sep 2011, at 02:25, Jonas Sicking wrote: > >>> OK, I understand... so is there a reason not to have a method for triggering the display of validation errors in addition to triggering a click on a submitControl? (I can understand not wanting duplication of functionality, but it would be great for clarity) >> >> I agree that this sounds like a good idea. >> >> One simple solution would be to make checkValidity take a optional >> boolean argument which defaults to false. If the function is called on >> a <form> and passed true, this instructs the UA to display the same UI >> as would be displayed if the form was submitted. If the function is >> called on a individual control and passed true, this instructs the UA >> to display any UI it would for that control. >> >> / Jonas > > > Exactly! http://twitter.com/#!/matiaslarsson/status/116887142516531201 :) I'd take a experimental gecko-patch if you write one :) / Jonas
Received on Thursday, 29 September 2011 09:25:48 UTC