Why Custom Validators WON'T work in FoxFire?

[Guest]

I am able fire my field validators in FireFox on the server side using...

Page.Validate()
If Not Page.IsValid Then
Exit Sub
End If

But the it won't fire Custom Validators. Anybody know why?

 

[TJS]

make sure the browser caps is updated in the config file
updates availble from http://slingfive.com/pages/code/browserCaps/

however, even with the udates, I find that vaidators do not always work as
advertised in Firefox browser, even though they may work fine in IE browser
for the same page.

When that happens I just write my own code to validate on the server side or
go with som external javascript validator file.

good luck.

 

[Michel de Becdelièvre]

make sure the browser caps is updated in the config file
updates availble from http://slingfive.com/pages/code/browserCaps/

however, even with the udates, I find that vaidators do not always work as
advertised in Firefox browser, even though they may work fine in IE
browser for the same page.

When that happens I just write my own code to validate on the server side
or go with som external javascript validator file.

You do not need to : google Paul Glavitch DOMValidator. Real good.

 

[Juan T. Llibre]

Make that "Glavich DOMValidator", not Glavitch.

Here's the Google link :

http://www.google.com/search?hl=en&lr=&c2coff=1&biw=1004&q=Glavich+DOMValidator&btnG=Search

 

[Peter Blum]

The Validators in ASP.NET 1.x were written using DHTML, a system specific to
IE and IE/Mac browsers. They simply do not provide client-side validation on
other browsers. ASP.NET 2.0 resolves this. So does my Professional
Validation And More, http://www.peterblum.com/vam/home.aspx, which greatly
improves all aspects of validation and data entry on web forms.

CustomValidators should always have a server side evaluation function. It
should be called by Page.Validate() unless you forget to hook it up or the
Validator is Enabled=false or Visible=false.
Additionally, if you use the ControlToValidate property, it will not be
called when the associated field has a blank value. If you need to support
blank values, do not assign ControlToValidate and make your evaluation
function refer to the control directly instead of using the value in the
Args parameter.

--- Peter Blum
www.PeterBlum.com
Email: (e-mail address removed)
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx

 

[Paul Glavich [MVP ASP.NET]]

Thanks for the the plug guys.

You can download them directly from here too.
http://www.theglavs.com/GlavTech/Downloads/DomValidators.zip