Comments on: ASP.NET Validators Do Not Fire in Firefox

By: Mark

Mark — Tue, 09 Dec 2008 02:15:23 +0000

Thanks for this post. I was working on a asp.net website someone else had built and this error was driving me nuts. Thank goodness for Google and kind people like you who post their solutions.

By: shereen

shereen — Tue, 09 Dec 2008 02:14:48 +0000

@tom: thanks for the comments. That makes absolutely no sense that you’d have to satisfy all form validators before IE will permit you to reset your form. Interesting scenario. Changing the xhtmlConformanceMode setting effectively resulted in the same behavior for both of us: consistency from both browsers. However, as you pointed out, that doesn’t necessarily mean we get the CORRECT behavior. Thanks for posting your answer, hopefully someone else will find it useful!

By: Tom von Alten

Tom von Alten — Tue, 09 Dec 2008 02:14:24 +0000

Found the answer: add the attribute CausesValidation=”false” to the control(s) in question.

By: Tom von Alten

Tom von Alten — Tue, 09 Dec 2008 02:14:08 +0000

Thanks for this post. I had the inverse problem: having developed with Firefox’s behavior, I was getting what I wanted with ValidateRequest=”false” set for the page, and controlling what, and when I validate with my codebehind. Come to find out IE fires the validators no matter what, breaking the form’s [CANCEL] button. One has to satisfy all the form validators before the inputs can be discarded? This is not intelligent behavior. As you found, by changing the Web.config xhtmlConformanceMode setting, I could get the same behavior from both Fx and IE. Unfortunately it’s the same WRONG behavior. So… how do we tell IE that thankyouverymuch, but we do NOT it to fire validators unless commanded?