I have run into a problem with a webApp. The app works fin, only when accessed via a Firefox browser, the validation controls fire, but prevent the page from posting even after all the required conditions have been met. I have changed several configurations after looking up articles on this issue and I have not found a working solution (in fact now my validation doesn't work at all when viewing using Firefox). IE handles the validation without problem. Is there an easy solution to this?

 

 

Thanks for any and all input,

 

PackAddikt42

 

 

PS: I have the most recent aspnet_client folder in the root directory of my site

Yeah, use IE! :) just kidding

Actually though, that seems to be Microsoft's approach. Hopefully they'll realize that a growing number of people are using browsers other than IE due to security concerns and start improving this.

Maybe someone else will have a better answer than me.

Jeff

Hi,

ASP.NET considers firefox to be a downlevel browser (you can change it in the machine.config) or override the settings in your web.config). Besides that the client side validation is written in JScript which is a dialect of Microsoft of the Javascript/Ecmascript standard.

Grz, Kris.

ASP.NET 1.x has written its client-side validation scripts using DHTML, the dialect of IE and IE/Mac. So it supports those browsers but not the DOM-based browsers like those based on Mozilla and Safari.

Third parties have created replacements for the validators that give you support of more browsers. I make one of the, Professional Validation And More. My solution addresses numerous other limitations of the Microsoft validation controls that continue to demand users write custom code and hacks.

ASP.NET 2.0 (now in beta) offers support for both DHTML and DOM browsers in client-side validation.

Peter,

While your products looks quite good, plugging them as an answer to a question really isn't all that helpful.  This is especially true since the cost of ownership is quite high for many 'hobby' developers. 

One of the challenges of answering questions here is that we don't know the background of the author. Certainly many hobby developers are not interested in spending money. Yet, I've had customers who are building very simple sites purchase my software because they get the technology they want without spending a lot of time or confronting the numerous technology issues of working in DHTML on multiple browsers.

My answer was an accurate representation of the options available. I have also published an article on ASP.NET validation that has helped elaborate on the subject: http://aspalliance.com/699.

ASP.NET 2.0 shipped yesterday and its validators now also work client-side on Firefox.