Without a testpage that contains the issue its really hard to propose a solution.
The problem with same-name fields in different forms is how error labels are created: If the element has no id, the name is used in the for-attribute of the label. This is likely to cause the issue. If you can't touch the existing code, implementing the showErrors-option could work. Jörn On Mon, Oct 27, 2008 at 12:11 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Naturally I can't get it to occur on a pure test page, which contains > just the form and the required javascript. > > http://www.rebeccamurphey.com/stuff/ds/form.html > > Any suggestions where to look for what might be causing this? One > suspicion I have is that there's another input element on the page > with the same name ("username"). However, it's not part of the same > form. Still, any chance that's having an impact? Unfortunately I'll be > hard-pressed to change either input name, because they are both tied > to existing code that I'd like to avoid modifying if at all > possibe ... > > On Oct 27, 4:39 am, "Jörn Zaefferer" <[EMAIL PROTECTED]> > wrote: >> The remote validation is supposed to do nothing until the ajax result >> is returned. Its probably a bug, though a testpage would help a lot to >> confirm that. >> >> Jörn >> >> On Mon, Oct 27, 2008 at 12:19 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> >> wrote: >> >> > I have a registration form that I'm trying to validate using >> > jquery.validate.js v1.2 with jQuery 1.2.6. >> >> > On the username field, I am doing remote validation to verify the >> > username does not already exist. When I blur out of the field, I >> > *always* get an error under the field telling me the username is >> > already taken, before the remote validation even has a chance to run. >> > If I then refocus the field, the error message goes away; when I blur >> > again, the error message doesn't re-appear. >> >> > The remote method is clearly returning the proper values (true if the >> > username is available, false if the username is taken). However, I >> > don't understand why the field is being marked invalid before the >> > remote method even runs. >> >> > Any ideas? >> >> > Thanks, >> > Rebeca
