Validation and Firefox(js scripts doesn''t fire)

[Juan T. Llibre]

re:

it sounds to me like people are saying that implementing the proper
browsercaps section within web.config should enable client side validation
on firefox ( and i assume netscape ? )

This quote from Peter Blum's post explains the issue :

1. ASP.NET 1.x outputs DHTML based scripts. Specifically, it uses
document.all[] to locate an element on the page. FireFox/Mozilla and most
other browsers use the W3C DOM standard, which does not have the
document.all[] statement.

Whether or not you setup browsercaps or event <@ Page
clientTarget="upLevel">, you still will not change how the web controls
identify their validators in the client-side Page_Validators array or within
the WebUIValidation.js file.

For more details, see:
http://aspnet.4guysfromrolla.com/articles/051204-1.aspx

2. Several vendors, including myself, have created replacements for the
validators that does handle most browsers in ASP.NET 1.x. My solution is
Professional Validation And More (http://www.peterblum.com/vam/home.aspx).

The article references another free solution, Paul Glavich's DOM Validators.
My software is more of a general upgrade to validation, not just a fix to
this particular problem.

3. ASP.NET 2.0 has been fixed to address their limitation. They are now
using document.getElementById() which is W3C DOM compliant.

---000---

I hope that make the issue clearer.




Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================

 

[Juan T. Llibre]

You did the right thing.

When you don't have any arguments left,
giving up is a very sensible attitude.

;-)



Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================

 

[WJ]

It is no longer a useful discussion. I mean - I
GGGGGGGGGAAAAAAAAVVVVVVVVVEEEEEE UPPPPPPPP !!! OKKKKKKK!

John

 

[Kevin Spencer]

Juan, you're just bad.

--
;-),

Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.

 

[gerry]

Hi Juan
I think there has been a vast muddying of the waters in this thread
thanks for the clarification

re:

it sounds to me like people are saying that implementing the proper
browsercaps section within web.config should enable client side validation
on firefox ( and i assume netscape ? )

This quote from Peter Blum's post explains the issue :

1. ASP.NET 1.x outputs DHTML based scripts. Specifically, it uses
document.all[] to locate an element on the page. FireFox/Mozilla and most
other browsers use the W3C DOM standard, which does not have the
document.all[] statement.

Whether or not you setup browsercaps or event <@ Page
clientTarget="upLevel">, you still will not change how the web controls
identify their validators in the client-side Page_Validators array or within
the WebUIValidation.js file.

For more details, see:
http://aspnet.4guysfromrolla.com/articles/051204-1.aspx

2. Several vendors, including myself, have created replacements for the
validators that does handle most browsers in ASP.NET 1.x. My solution is
Professional Validation And More (http://www.peterblum.com/vam/home.aspx).

The article references another free solution, Paul Glavich's DOM Validators.
My software is more of a general upgrade to validation, not just a fix to
this particular problem.

3. ASP.NET 2.0 has been fixed to address their limitation. They are now
using document.getElementById() which is W3C DOM compliant.

---000---

I hope that make the issue clearer.




Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================

Hi ,

without jumping into the flames,
it sounds to me like people are saying that implementing the proper
browsercaps section within web.config should enable client side validation
on firefox ( and i assume netscape ? )

it is my experience that this is not so. no java script is renedered in
firefox regardless of these settings.
I have been used the browsercaps from
http://slingfive.com/pages/code/browserCaps for a long time now.
This does fix the html/css rendering issues but has not had any effect on
script renedering.

Am I misunderstanding this point or do I still have something incorrectly
configured somewhere ?

Gerry



most
modern browsers the
simple "required Field
Validators using should I
have to

 

[Guest]

I've been using .Net to develop some fairly extensive web forms. I haven't
had any problems with the validation controls in FireFox or other non-IE
browsers (including regex parsing). Yes, you do need JavaScript turned on in
FireFox for everything to work, but you need it switched on in IE too.
ASP.Net relies almost completely on client side JavaScript. These days though
there aren't too many clients out there that don't have JavaScript so I don't
see it as being a huge issue.

One thing I know to be an issue is the treeview controls. The default
asp.net ones only work in IE. You can get third party ones that work in all
browsers though.

If you are having problems with JavaScript in FireFox, have a look at the
JavaScript console (Tools / JavaScript Console). It's quite helpful.

I have used customised browsercaps sections, but I think they just relate to
the type of HTML that is generated by the server rather than any kind of
JavaScript compatibility.

(Having said all that, I was recently amazed by our 'Lead Developer' who
managed to create a very simple asp.net app that didn't work at all in
FireFox)

 

[gerry]

could you publish your browser caps section and post a link to it ?
better yet - can you additionally post a link to your site that has client
side validators that work in firefox ?

I have found that validators do not generate any client side javascript for
firefox - absolutely none.

I had asked previously in this thread if this was just me doing something
wrong and had it confirmed that this was the way asp.net worked.
Are you certain that the validators are really working on the client instead
of doing a roundtrip back to the server ?

Gerry