its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
45  4655 
My understanding is that .net doesn't support client side validation in
anything other than ie. Yay.
It does however validate on the server for these users... hope that
helps?
..Net is an advanced system that is run on MS/Windows platform only ! Period
! Certain features will not work with non-ms browsers as you found out. As a
result, you may want to tell your users that to use your website, MSIE is
required. However, if you wish to allow all platforms to participate in your
website, then you have two choices: a) Do not use .Net period and or b) Use
..Net but do not use advanced features offered in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
Thx Mr John
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found out. As
a result, you may want to tell your users that to use your website, MSIE is
required. However, if you wish to allow all platforms to participate in
your website, then you have two choices: a) Do not use .Net period and or b)
Use .Net but do not use advanced features offered in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
Bit of a sweeping statement. ASP.NET just outputs data for the browser to
render. Theoretically, the output is browser agnostic. Of course,
practically, the designers of ASP.NET share the canteen with the designers
of MSIE, so it's natural that they get together over a couple of milk shakes
and say things like "wouldn't the internet be great if we had client side
validation rather than shunting everything back and forth to the server". An
lo and behold, the IE team implement support for ASP.NET latest trick.
But I strongly disagree that ASP.NET should only be used with IE. Fact is
that market share is moving away from IE, although IE is still dominant. You
really have to cater for as much of the market that you practically can. At
the moment we're talking about desktop browsers. ASP.NET is very capable of
supplying content for mobile devices too.
Of course, to cater for most browsers you have to write your app based on
the minimum shared spec. It's true that this precludes many "advanced"
features, but often these were just eye candy anyway. Your user doesn't
really *need* Java menus.
BTW the reason the page doesn't validate with Firefox could be because you
have java/script turned off.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found out. As
a result, you may want to tell your users that to use your website, MSIE is
required. However, if you wish to allow all platforms to participate in
your website, then you have two choices: a) Do not use .Net period and or b)
Use .Net but do not use advanced features offered in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
"KMA" <km*@chum.com> wrote in message news:dg**********@atlas.ip-plus.net...
But I strongly disagree that ASP.NET should only be used with IE. Fact is
that market share is moving away from IE, although IE is still dominant.
You really have to cater for as much of the market that you practically
can. At
the moment we're talking about desktop browsers
Then we, developer should take care not to base our logic on one central
platform such as .Net. We should demand .Net creator (MS) to accomodate
other tools as well. Not just MSIE. So far, MS does not comply. Why do .Net
Validator controls work very well on MSIE but not on other browsers ?
Because "control of market by MS", period! I am not anti-MS, it is useless
to yell at a billionaire. I am just saying that, us, the developers, make
sure that stuffs donot work on non-MSIE should not be implemented because
they break anyway. Why use them.
ASP.NET is very capable of
supplying content for mobile devices too.
I am not up to speed on mobile devices. However, do these tiny devices host
non MS tools too ? Such as FF and NS ? I know mobile device only works with
Windows platforms (I could be wrong) ?
Of course, to cater for most browsers you have to write your app based on
the minimum shared spec. It's true that this precludes many "advanced"
features, but often these were just eye candy anyway. Your user doesn't
really *need* Java menus.
Well. My intention is mainly for KISS. If the tool itself (.net) already
provides such features as client validator controls, then why should I have
to write my own codes to do the same thing on the server ? It is a
duplication of effort that should be avoided. I do like the client validator
controls offered by Asp.Net, and I told my clients that you must use IE. In
fact, 99.9% of my clients are MS/Windows (98SE, and XP Home or Pro). These
OSes ship with MSIE. If other browsers don't work, then use IE.
BTW the reason the page doesn't validate with Firefox could be because you
have java/script turned off.
I tried this with NS too and it broke! On my website, I offered other JS
features such as onFocus, onBlur and doubleclick, etc, etc... and most of
those work fine on non MS browsers. So I know that my clients do enable JS.
Otherwise, Asp.Net form would not work in the 1st place. I hope VS2k5 will
be improved and that Validator controls would work with other browsers
(would be nice)
John
> So are you saying it won't work
Are you insane? If you read the article
( http://asptoday.com/Content.aspx?id=2339), it explains how ASP.Net uses a
config section called <browserCaps> to enable the server-side components to
interact with a variety of browsers. In addition, it describes the problem
with the version of browserCaps that is installed with the .Net Framework
1.1. Finally, it details how to rememdy the issue, and has a link to a
complete and excellent browserCaps config section that can be added to the
machine.config file, and instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:el**************@TK2MSFTNGP14.phx.gbl... So are you saying it won't work
<sh**********@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com... Try
http://asptoday.com/Content.aspx?id=2339
Regards
C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
http://www.geocities.com/dotnetinterviews/
Yuor understanding is wrong. See http://asptoday.com/Content.aspx?id=2339.
It explains how ASP.Net uses a config section called <browserCaps> to enable
the server-side components to interact with a variety of browsers. In
addition, it describes the problem with the version of browserCaps that is
installed with the .Net Framework 1.1. Finally, it details how to rememdy
the issue, and has a link to a complete and excellent browserCaps config
section that can be added to the machine.config file, and instructions on
how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
"Waldorf" <gl***********@gmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com... My understanding is that .net doesn't support client side validation in
anything other than ie. Yay.
It does however validate on the server for these users... hope that
helps?
> .Net is an advanced system that is run on MS/Windows platform only ! Period !
Incorrect! Period! See http://asptoday.com/Content.aspx?id=2339. It explains
how ASP.Net uses a config section called <browserCaps> to enable the
server-side components to interact with a variety of browsers. In addition,
it describes the problem with the version of browserCaps that is installed
with the .Net Framework 1.1. Finally, it details how to rememdy the issue,
and has a link to a complete and excellent browserCaps config section that
can be added to the machine.config file, and instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found
out. As a result, you may want to tell your users that to use your
website, MSIE is required. However, if you wish to allow all platforms to
participate in your website, then you have two choices: a) Do not use .Net
period and or b) Use .Net but do not use advanced features offered in
.Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
I wouldn't thank him yet. See my replies to this thread.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:ur**************@tk2msftngp13.phx.gbl... Thx Mr John
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found out.
As
a result, you may want to tell your users that to use your website, MSIE is
required. However, if you wish to allow all platforms to participate in
your website, then you have two choices: a) Do not use .Net period and or b)
Use .Net but do not use advanced features offered in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... > its seems asp.net validation doesn't fire when using FireFox?
> Tested a page and it doesn't fire.
> It seems the javascript doesn't fire
> Any ideas?
>
>
You make some good points. However, see my replies to this thread. Most
ASP.Net Controls are browser-aware, and use the <browserCaps> Configuration
Section in the machine.config, or web.config file. This file can easily be
modified, as per this article: http://asptoday.com/Content.aspx?id=2339.
The best news is, in the .Net platform 2.0, the <broserCaps> Configuration
section has been removed, and replaced with a folder in the CONFIG folder
containing multiple *.browser files, which contain detailed BrowserCaps for
many browsers, a much more complete collection than in the .Net Platform
1.1. And of course, you can modify and add to them as well, and they all
conform to the MSXML XML Standard. Thes include the most popular browsers,
such as Netscape, AOL, FireFox, Safari, and other Mozilla versions, as well
as a number of minor players and a huge selection of portable device
browsers.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
Neither a follower nor a lender be.
"KMA" <km*@chum.com> wrote in message news:dg**********@atlas.ip-plus.net... Bit of a sweeping statement. ASP.NET just outputs data for the browser to
render. Theoretically, the output is browser agnostic. Of course,
practically, the designers of ASP.NET share the canteen with the designers
of MSIE, so it's natural that they get together over a couple of milk
shakes
and say things like "wouldn't the internet be great if we had client side
validation rather than shunting everything back and forth to the server".
An
lo and behold, the IE team implement support for ASP.NET latest trick.
But I strongly disagree that ASP.NET should only be used with IE. Fact is
that market share is moving away from IE, although IE is still dominant.
You
really have to cater for as much of the market that you practically can.
At
the moment we're talking about desktop browsers. ASP.NET is very capable
of
supplying content for mobile devices too.
Of course, to cater for most browsers you have to write your app based on
the minimum shared spec. It's true that this precludes many "advanced"
features, but often these were just eye candy anyway. Your user doesn't
really *need* Java menus.
BTW the reason the page doesn't validate with Firefox could be because you
have java/script turned off.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found out.
As
a result, you may want to tell your users that to use your website, MSIE is
required. However, if you wish to allow all platforms to participate in
your website, then you have two choices: a) Do not use .Net period and or b)
Use .Net but do not use advanced features offered in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... > its seems asp.net validation doesn't fire when using FireFox?
> Tested a page and it doesn't fire.
> It seems the javascript doesn't fire
> Any ideas?
>
>
"WJ" <Jo*******@HotMail.Com> wrote in message
news:O7*************@TK2MSFTNGP15.phx.gbl...
"KMA" <km*@chum.com> wrote in message
news:dg**********@atlas.ip-plus.net...
But I strongly disagree that ASP.NET should only be used with IE. Fact
is that market share is moving away from IE, although IE is still dominant.
You really have to cater for as much of the market that you practically
can. At
the moment we're talking about desktop browsers
Then we, developer should take care not to base our logic on one central
platform such as .Net. We should demand .Net creator (MS) to accomodate
other tools as well. Not just MSIE. So far, MS does not comply. Why do
..Net Validator controls work very well on MSIE but not on other browsers ?
Because "control of market by MS", period! I am not anti-MS, it is useless
to yell at a billionaire. I am just saying that, us, the developers, make
sure that stuffs donot work on non-MSIE should not be implemented because
they break anyway. Why use them.
ASP.NET is very capable of
supplying content for mobile devices too.
I am not up to speed on mobile devices. However, do these tiny devices
host non MS tools too ? Such as FF and NS ? I know mobile device only works
with Windows platforms (I could be wrong) ?
Yep. Many mobile devices run proprietary browsing software, not MSIE,
Firefox or any other desktop software. They just render HTML.
Of course, to cater for most browsers you have to write your app based
on the minimum shared spec. It's true that this precludes many "advanced"
features, but often these were just eye candy anyway. Your user doesn't
really *need* Java menus.
Well. My intention is mainly for KISS. If the tool itself (.net) already
provides such features as client validator controls, then why should I
have to write my own codes to do the same thing on the server ? It is a
duplication of effort that should be avoided.
And how do you know that the information really was validated client side?
The way I see it, client side validation is just a whistle and bell to help
the user fill out the form quicker. The actual decision about whether the
post is good should be made sever side.
I do like the client validator
controls offered by Asp.Net, and I told my clients that you must use IE.
In fact, 99.9% of my clients are MS/Windows (98SE, and XP Home or Pro). These
OSes ship with MSIE. If other browsers don't work, then use IE.
Well, you can make this stipulation when you know your clients, or better
still are in a position to control their choices, ie corporate intranet. But
if you run a shopping site, you can't be so regimented. Imagine walking into
a regular store and being turned away because you're wearing jeans.
BTW the reason the page doesn't validate with Firefox could be because
you have java/script turned off.
I tried this with NS too and it broke! On my website, I offered other JS
features such as onFocus, onBlur and doubleclick, etc, etc... and most of
those work fine on non MS browsers. So I know that my clients do enable
JS. Otherwise, Asp.Net form would not work in the 1st place. I hope VS2k5 will
be improved and that Validator controls would work with other browsers
(would be nice)
I can't see how a new version of VS will help. It's the client side that
blocks validation (or rather the client side processing that runs it). The
reason it's blocked is out of real or imagined security concerns. These
concerns aren't going to disappear so I figure that feature poor but
security rich browsing will become more popular. None of this is
incompatible with ASP.NET philosophy though.
John
The javascript it produces is Microsoft specific, and will not work in
anything other that IE - trust me I have been through this pain
barrier! Client side validation will not run in Firefox, but server
side will.
My solution has been to run all validation on the server, therefore
making sure that it all runs.
So ASP.NET isn't just for IE6.0 then? :-)
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period !
Incorrect! Period! See http://asptoday.com/Content.aspx?id=2339. It
explains how ASP.Net uses a config section called <browserCaps> to enable the
server-side components to interact with a variety of browsers. In
addition, it describes the problem with the version of browserCaps that is installed
with the .Net Framework 1.1. Finally, it details how to rememdy the issue,
and has a link to a complete and excellent browserCaps config section that
can be added to the machine.config file, and instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you
found out. As a result, you may want to tell your users that to use your
website, MSIE is required. However, if you wish to allow all platforms
to participate in your website, then you have two choices: a) Do not use
..Net period and or b) Use .Net but do not use advanced features offered in
.Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
There is some incorrect information being given here.
Here are the facts:
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.
--- Peter Blum www.PeterBlum.com
Email: PL****@PeterBlum.com
Creator of "Professional Validation And More" at http://www.peterblum.com/vam/home.aspx
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period !
Incorrect! Period! See http://asptoday.com/Content.aspx?id=2339. It
explains how ASP.Net uses a config section called <browserCaps> to enable
the server-side components to interact with a variety of browsers. In
addition, it describes the problem with the version of browserCaps that is
installed with the .Net Framework 1.1. Finally, it details how to rememdy
the issue, and has a link to a complete and excellent browserCaps config
section that can be added to the machine.config file, and instructions on
how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you found
out. As a result, you may want to tell your users that to use your
website, MSIE is required. However, if you wish to allow all platforms to
participate in your website, then you have two choices: a) Do not use
.Net period and or b) Use .Net but do not use advanced features offered
in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
Kevin Spencer wrote: Most
ASP.Net Controls are browser-aware, and use the <browserCaps> Configuration
Section in the machine.config, or web.config file. This file can easily be
modified, as per this article: http://asptoday.com/Content.aspx?id=2339.
But note that it says at the end:
"For instance, it might still not help you with client-side
validators, as even if Firefox is recognized as an uplevel browser, in
many cases these validators are still not W3C complaint and may not work
properly anyway outside IE."
That is also my experience, the problem with the client-side validation
code that ASP.NET 1.x generates is that is is scripted against the IE
DOM and if you have ASP.NET serve those scripts to Mozilla, Netscape or
Firefox the user might end up with client-side script errors and not
client-side validation.
--
Martin Honnen --- MVP XML http://JavaScript.FAQTs.com/
the clientside validation only works with IE, as it uses the IE dom, not the
W3C dom, so asp.net suppresses the output if the browser is not IE. the
serverside validation works with any browser.
asp.net 2.0 is supposed to remove this restriction.
-- bruce (sqlwork.com)
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl... its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
Heck no, it's for everybody! :-D
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"KMA" <km*@chum.com> wrote in message news:dg**********@atlas.ip-plus.net... So ASP.NET isn't just for IE6.0 then? :-)
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl... > .Net is an advanced system that is run on MS/Windows platform only !
> Period !
Incorrect! Period! See http://asptoday.com/Content.aspx?id=2339. It
explains how ASP.Net uses a config section called <browserCaps> to enable the
server-side components to interact with a variety of browsers. In
addition, it describes the problem with the version of browserCaps that is
installed
with the .Net Framework 1.1. Finally, it details how to rememdy the
issue,
and has a link to a complete and excellent browserCaps config section
that
can be added to the machine.config file, and instructions on how to do
it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... > .Net is an advanced system that is run on MS/Windows platform only !
> Period ! Certain features will not work with non-ms browsers as you found > out. As a result, you may want to tell your users that to use your
> website, MSIE is required. However, if you wish to allow all platforms to > participate in your website, then you have two choices: a) Do not use .Net > period and or b) Use .Net but do not use advanced features offered in
> .Net.
>
> John
>
> "Pat" <na********@hotmail.com> wrote in message
> news:ej**************@TK2MSFTNGP14.phx.gbl...
>> its seems asp.net validation doesn't fire when using FireFox?
>> Tested a page and it doesn't fire.
>> It seems the javascript doesn't fire
>> Any ideas?
>>
>>
>
>
Well, Peter, perhaps "incomplete" is a more appropriate term. Still, the
problem you pointed out is serious, and it's good to know where to find the
necessary fixes. I will forward the information to our UI guy!
I've been rather astounded with .Net 2.0 in general, including ASP.Net 2.0.
Microsoft has improved an already excellent product by leaps and bounds.
Lately I've been having a lot of fun with Generics.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"Peter Blum" <PL****@Blum.info> wrote in message
news:e$**************@TK2MSFTNGP14.phx.gbl... There is some incorrect information being given here.
Here are the facts:
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.
--- Peter Blum
www.PeterBlum.com
Email: PL****@PeterBlum.com
Creator of "Professional Validation And More" at
http://www.peterblum.com/vam/home.aspx
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period !
Incorrect! Period! See http://asptoday.com/Content.aspx?id=2339. It
explains how ASP.Net uses a config section called <browserCaps> to enable
the server-side components to interact with a variety of browsers. In
addition, it describes the problem with the version of browserCaps that
is installed with the .Net Framework 1.1. Finally, it details how to
rememdy the issue, and has a link to a complete and excellent browserCaps
config section that can be added to the machine.config file, and
instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:OU**************@TK2MSFTNGP10.phx.gbl... .Net is an advanced system that is run on MS/Windows platform only !
Period ! Certain features will not work with non-ms browsers as you
found out. As a result, you may want to tell your users that to use your
website, MSIE is required. However, if you wish to allow all platforms
to participate in your website, then you have two choices: a) Do not use
.Net period and or b) Use .Net but do not use advanced features offered
in .Net.
John
"Pat" <na********@hotmail.com> wrote in message
news:ej**************@TK2MSFTNGP14.phx.gbl...
its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
True, see Peter Blum's response (and fix). I haven't used the validators
(rolled my own), so I haven't had much experience in that area. Still, the
browserCaps do improve the appearance of the HTML in the target browsers
tremendously, particularly in the ara of CSS.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"Martin Honnen" <ma*******@yahoo.de> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
Kevin Spencer wrote:
Most ASP.Net Controls are browser-aware, and use the <browserCaps>
Configuration Section in the machine.config, or web.config file. This
file can easily be modified, as per this article:
http://asptoday.com/Content.aspx?id=2339.
But note that it says at the end:
"For instance, it might still not help you with client-side validators,
as even if Firefox is recognized as an uplevel browser, in many cases
these validators are still not W3C complaint and may not work properly
anyway outside IE."
That is also my experience, the problem with the client-side validation
code that ASP.NET 1.x generates is that is is scripted against the IE DOM
and if you have ASP.NET serve those scripts to Mozilla, Netscape or
Firefox the user might end up with client-side script errors and not
client-side validation.
--
Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/
"KMA" <km*@chum.com> wrote in message news:dg**********@atlas.ip-plus.net...
And how do you know that the information really was validated client side?
I just described generically about common validation logics such as "field
is required".... Yes, serious stuffs must also be checked on the server. No
doubt.
The way I see it, client side validation is just a whistle and bell to
help the user fill out the form quicker.
Not really. JS is as serious as server side c# code. It provides good
experiences to your visitors. Example: If I have 20 fields that are mandate.
I rather have Required Validator controls done on site (client).
The actual decision about whether the post is good should be made sever
side.
Not always.
if you run a shopping site, you can't be so regimented. Imagine walking
into
a regular store and being turned away because you're wearing jeans.
Sure. You just tell your users that it will be a little bit slow (but it
works) if they do not use the MSIE (in this context).
John
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl... <browserCaps>
Sound like "stitching" process in a sweat shop. A d/html page should be able
to handle simple client side JS to validate a "required field" on any modern
browsers (out of the box). Don't give me all these craps. It is very simple:
A browser war, a control process. No more no less.
John
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ey**************@TK2MSFTNGP14.phx.gbl... re: .Net is an advanced system that is run on MS/Windows platform only !
Period
I wonder what :
http://go-mono.com/archive/xsp-0.10.html
and
http://httpd.apache.org/cli/mod_aspdotnet
are all about... ?
ASP.NET also runs on FreeBSD, with the same XSP server :
http://forge.novell.com/modules/xfmo...ect/?bsd-sharp
Please update your information.
No thanks. In a perfect world, there should be many systems to choose from.
We already have a .Net system that mimics Java system. I would rather stick
with MS/.Net system because it is working on its Windows platform very well.
I would like to see the software industry to dream up something else to
rival .Net and Java. I sure don't feel very comfortable with monopoly!
John
re: A d/html page should be able to handle simple client side JS to validate a "required
field" on any modern browsers (out of the box).
How does a page validate anything client-side ?
Client-side validation requires a browser's interpretation.
The server can validate a page server-side,
but the client-side validation must be made by the browser.
The modification of the <browserCaps> section of web.config
*enables* that the correct dhtml is sent to those browsers which
don't interpret dhtml like IE does.
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" <Jo*******@HotMail.Com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl...
<browserCaps>
Sound like "stitching" process in a sweat shop. A d/html page should be able to handle
simple client side JS to validate a "required field" on any modern browsers (out of the
box). Don't give me all these craps. It is very simple: A browser war, a control
process. No more no less.
John
Great side-stepping!
Your statement was : .Net is an advanced system that is run on MS/Windows platform only ! Period.
You are flat-out wrong, as demonstrated by the fact that .NET
runs perfectly well on systems which are *not* MS/Windows platform.
Period.
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" <Jo*******@HotMail.Com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ey**************@TK2MSFTNGP14.phx.gbl... re: .Net is an advanced system that is run on MS/Windows platform only ! Period
I wonder what :
http://go-mono.com/archive/xsp-0.10.html
and
http://httpd.apache.org/cli/mod_aspdotnet
are all about... ?
ASP.NET also runs on FreeBSD, with the same XSP server :
http://forge.novell.com/modules/xfmo...ect/?bsd-sharp
Please update your information.
No thanks. In a perfect world, there should be many systems to choose from. We already
have a .Net system that mimics Java system. I would rather stick with MS/.Net system
because it is working on its Windows platform very well. I would like to see the
software industry to dream up something else to rival .Net and Java. I sure don't feel
very comfortable with monopoly!
John
Kevin
I was insane but i work up .
Are you in this mode sometimes too:)
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:em*************@TK2MSFTNGP09.phx.gbl... So are you saying it won't work
Are you insane? If you read the article
(http://asptoday.com/Content.aspx?id=2339), it explains how ASP.Net uses a
config section called <browserCaps> to enable the server-side components
to interact with a variety of browsers. In addition, it describes the problem
with the version of browserCaps that is installed with the .Net Framework
1.1. Finally, it details how to rememdy the issue, and has a link to a
complete and excellent browserCaps config section that can be added to the
machine.config file, and instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:el**************@TK2MSFTNGP14.phx.gbl... So are you saying it won't work
<sh**********@yahoo.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com... Try
http://asptoday.com/Content.aspx?id=2339
Regards
C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question book
http://www.geocities.com/dotnetinterviews/
> Sound like "stitching" process in a sweat shop. A d/html page should be able to handle simple client side JS to validate a "required field" on any
modern browsers (out of the box). Don't give me all these craps. It is
very simple: A browser war, a control process. No more no less.
I suppose you might say the same thing about all of the other Configuration
elements stored in the many .Net Configuration files stored on the server
and in the web application itself.
The purpose of Configuration files is to be able to modify globally-used
data without having to create/compile/extend a new version of a class
library or assembly. Configuration files contain run-time settings, security
settings, paths, connection strings, and a host of other data that may
change at any time during the lifetime of an application. As browsers and
HTML are continually in the process of being developed, revised, enhanced,
and extended, and as the scheduling of changes to the many different types
of browsers used worldwide is in no way synchronized with other browser
releases, or the development cycle of the .Net platform, it is only logical
to make browser capabilities a Configuration element.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl...
<browserCaps>
Sound like "stitching" process in a sweat shop. A d/html page should be
able to handle simple client side JS to validate a "required field" on any
modern browsers (out of the box). Don't give me all these craps. It is
very simple: A browser war, a control process. No more no less.
John
> We already have a .Net system that mimics Java system.
..Net no more mimics Java than the automobile mimics the horse and buggy.
Both the horse and buggy and the automobile have wheels. Both the horse and
buggy and the automobile have a passenger compartment. Both the horse and
buggy and the automobile have an "engine" that provides motility to the
vehicle. The automobile, however, is a vast improvement over the horse an
buggy, with greater power, more security, and a host of features that the
horse and buggy can not provide. The .Net platform is to Java what the
automobile is to the horse and buggy. It does not "mimic" Java. Rather, it
does what Java does, but it does it better, faster, and smarter than Java,
and it can do much MORE than Java.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"WJ" <Jo*******@HotMail.Com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:ey**************@TK2MSFTNGP14.phx.gbl... re: .Net is an advanced system that is run on MS/Windows platform only !
Period
I wonder what :
http://go-mono.com/archive/xsp-0.10.html
and
http://httpd.apache.org/cli/mod_aspdotnet
are all about... ?
ASP.NET also runs on FreeBSD, with the same XSP server :
http://forge.novell.com/modules/xfmo...ect/?bsd-sharp
Please update your information.
No thanks. In a perfect world, there should be many systems to choose
from. We already have a .Net system that mimics Java system. I would
rather stick with MS/.Net system because it is working on its Windows
platform very well. I would like to see the software industry to dream up
something else to rival .Net and Java. I sure don't feel very comfortable
with monopoly!
John
> I was insane but i work up . Are you in this mode sometimes too:)
Not as long as I take my meds! ;-)
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:Oc**************@TK2MSFTNGP15.phx.gbl... Kevin
I was insane but i work up .
Are you in this mode sometimes too:)
"Kevin Spencer" <ke***@DIESPAMMERSDIEtakempis.com> wrote in message
news:em*************@TK2MSFTNGP09.phx.gbl... > So are you saying it won't work
Are you insane? If you read the article
(http://asptoday.com/Content.aspx?id=2339), it explains how ASP.Net uses
a
config section called <browserCaps> to enable the server-side components
to interact with a variety of browsers. In addition, it describes the
problem
with the version of browserCaps that is installed with the .Net Framework
1.1. Finally, it details how to rememdy the issue, and has a link to a
complete and excellent browserCaps config section that can be added to
the
machine.config file, and instructions on how to do it!
--
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"Patrick.O.Ige" <pa********@optusnet.com.au> wrote in message
news:el**************@TK2MSFTNGP14.phx.gbl... > So are you saying it won't work
>
> <sh**********@yahoo.com> wrote in message
> news:11**********************@g14g2000cwa.googlegr oups.com...
>> Try
>> http://asptoday.com/Content.aspx?id=2339
>>
>>
>> Regards
>> C#, VB.NET , SQL SERVER , UML , DESIGN Patterns Interview question
>> book
>> http://www.geocities.com/dotnetinterviews/
>>
>
>
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:eb**************@TK2MSFTNGP10.phx.gbl... Great side-stepping!
I think I answered your post right on target. I think you are one who
side-stepping, not me.
Your statement was : .Net is an advanced system that is run on MS/Windows platform only !
Period.
You are flat-out wrong, as demonstrated by the fact that .NET
runs perfectly well on systems which are *not* MS/Windows platform.
And you kept avoiding my concern and or misunderstood my statement about
".Net runs on MS/Windows platform only"... and you kept referring me to
other silly mono thing. Yes, I am aware of these mono things, but Mono is
not cross-platform, it is a separate system that requires to be installed on
a separate OS (Unix/Linux). If one has to install more than one systems
(MS.Net and Mono.Net) on a single box to develop a same system using both
systems, then it is not considered as cross-platform. Here again, let me
explain to you: What I meant here is that a true "cross-platform" system
should be installed once, like Sun/Java system on a MS/Windows OS,
developers (you and I and others here) then develop our applications and
deploy our final products to other platforms of our choice.
IOW, MS should port .Net to other platform too, just like Sun/Java. Im
seating on one chair with one OS, one keyboard, & one mice, write a web form
that runs on both Windows and Unix ! I do not want to install another vendor
..Net system on my PC. it is silly to do that now a day, that is not
cross-platform, OK !
In short, my statement is still true: .Net fails do what Java can in term of
x-platform concept. That is: It can only run on Windows Oses.
John
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2*****************@TK2MSFTNGP15.phx.gbl... re: A d/html page should be able to handle simple client side JS to validate
a "required field" on any modern browsers (out of the box).
How does a page validate anything client-side ?
Client-side validation requires a browser's interpretation.
The server can validate a page server-side,
but the client-side validation must be made by the browser.
All I care is Java Script is universal, and it has been working on most
modern browsers that the current market offers. If it fails to validate a
simple "required field" request on the client browser, then it is broken,
incompatible, considered as a bug, monopoly, you name it. On top of that, if
the same page can implement onBlur and onFocus events using the same script
engine, then it should also work with the simple "required field" validator
component and I should not have to code browsercaps mess.
Why does it work on one and not the others ? Are Asp.Net Required Field
Validators using different JS engine than onBlur, onFocus, onDoubleClick...?
Why should I have to remember which one requires browsercap settings. That's
bad design my friend! NO GOOD!!!
John
re: Mono is not cross-platform
But it is. It runs on Linux, FreeBSD, Unix, etc.
ASP.NET is also cross-platform, since it will run on different OS's.
re:it is a separate system that requires to be installed on a separate OS (Unix/Linux).
Isn't that what "cross-platform" means ?
That the application will run on different platforms/OS's ?
re: What I meant here is that a true "cross-platform" system should be installed once
What you should have meant is that a true "cross-platform"
system should be *compiled* once but, in practice, there's
tweaks for each platform which require re-compilation, even for Java.
re: IOW, MS should port .Net to other platform too, just like Sun/Java.
MS's idea is that 3rd party developers can do the porting.
That way, .NET can be improved by 3rd party developers.
Java developers are frozen to Sun's specification for Java.
You may think that freezing specs is good.
I think it's not too good.
re: .Net fails do what Java can in term of x-platform concept. That is: It can only run on
Windows Oses.
But, it *does* run on other OS's, as shown.
It does *not* only run on Windows.
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" <Jo*******@HotMail.Com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:eb**************@TK2MSFTNGP10.phx.gbl... Great side-stepping!
I think I answered your post right on target. I think you are one who side-stepping, not
me.
Your statement was : .Net is an advanced system that is run on MS/Windows platform only ! Period.
You are flat-out wrong, as demonstrated by the fact that .NET
runs perfectly well on systems which are *not* MS/Windows platform.
And you kept avoiding my concern and or misunderstood my statement about ".Net runs on
MS/Windows platform only"... and you kept referring me to other silly mono thing. Yes, I
am aware of these mono things, but Mono is not cross-platform, it is a separate system
that requires to be installed on a separate OS (Unix/Linux). If one has to install more
than one systems (MS.Net and Mono.Net) on a single box to develop a same system using
both systems, then it is not considered as cross-platform. Here again, let me explain to
you: What I meant here is that a true "cross-platform" system should be installed once,
like Sun/Java system on a MS/Windows OS, developers (you and I and others here) then
develop our applications and deploy our final products to other platforms of our choice.
IOW, MS should port .Net to other platform too, just like Sun/Java. Im seating on one
chair with one OS, one keyboard, & one mice, write a web form that runs on both Windows
and Unix ! I do not want to install another vendor .Net system on my PC. it is silly to
do that now a day, that is not cross-platform, OK !
In short, my statement is still true: .Net fails do what Java can in term of x-platform
concept. That is: It can only run on Windows Oses.
John
re: All I care is Java Script is universal
You will have to live with, and die by, JavaScript, then.
re: then it should also work with the simple "required field" validator component and I
should not have to code browsercaps mess.
But, it does work, as long as you identify the browser
and send it HTML/scripts it understands.
The whole "I shouldn't have to code" idea is just lazyness, to me.
I'm not saying that it should be harder/more complicated than
it needs to be, but requiring "no code" is just absurd.
That's how we make a living : by writing code!
Get used to it...or go to a different platform.
Then you''ll see what complex, *really hard to grasp* code is.
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" <Jo*******@HotMail.Com> wrote in message
news:%2******************@TK2MSFTNGP14.phx.gbl... "Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2*****************@TK2MSFTNGP15.phx.gbl... re: A d/html page should be able to handle simple client side JS to validate a "required
field" on any modern browsers (out of the box).
How does a page validate anything client-side ?
Client-side validation requires a browser's interpretation.
The server can validate a page server-side,
but the client-side validation must be made by the browser.
All I care is Java Script is universal, and it has been working on most modern browsers
that the current market offers. If it fails to validate a simple "required field"
request on the client browser, then it is broken, incompatible, considered as a bug,
monopoly, you name it. On top of that, if the same page can implement onBlur and onFocus
events using the same script engine, then it should also work with the simple "required
field" validator component and I should not have to code browsercaps mess.
Why does it work on one and not the others ? Are Asp.Net Required Field Validators using
different JS engine than onBlur, onFocus, onDoubleClick...? Why should I have to
remember which one requires browsercap settings. That's bad design my friend! NO GOOD!!!
John
4
How about providing a reasoned rebuttal, instead of a trivial comment ?
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" <Jo*******@HotMail.Com> wrote in message
news:um**************@TK2MSFTNGP14.phx.gbl... mind-boggling
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
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:Om**************@TK2MSFTNGP14.phx.gbl... re:All I care is Java Script is universal
You will have to live with, and die by, JavaScript, then.
re: then it should also work with the simple "required field" validator
component and I should not have to code browsercaps mess.
But, it does work, as long as you identify the browser
and send it HTML/scripts it understands.
The whole "I shouldn't have to code" idea is just lazyness, to me.
I'm not saying that it should be harder/more complicated than
it needs to be, but requiring "no code" is just absurd.
That's how we make a living : by writing code!
Get used to it...or go to a different platform.
Then you''ll see what complex, *really hard to grasp* code is.
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" <Jo*******@HotMail.Com> wrote in message
news:%2******************@TK2MSFTNGP14.phx.gbl... "Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:%2*****************@TK2MSFTNGP15.phx.gbl... re:
A d/html page should be able to handle simple client side JS to
validate a "required field" on any modern browsers (out of the box).
How does a page validate anything client-side ?
Client-side validation requires a browser's interpretation.
The server can validate a page server-side,
but the client-side validation must be made by the browser.
All I care is Java Script is universal, and it has been working on most
modern browsers that the current market offers. If it fails to validate a simple
"required field" request on the client browser, then it is broken, incompatible,
considered as a bug, monopoly, you name it. On top of that, if the same page can implement
onBlur and onFocus events using the same script engine, then it should also work with the
simple "required field" validator component and I should not have to code browsercaps
mess.
Why does it work on one and not the others ? Are Asp.Net Required Field
Validators using different JS engine than onBlur, onFocus, onDoubleClick...? Why should I
have to remember which one requires browsercap settings. That's bad design my
friend! NO GOOD!!!
John
4
It is no longer a useful discussion. I mean - I
GGGGGGGGGAAAAAAAAVVVVVVVVVEEEEEE UPPPPPPPP !!! OKKKKKKK!
John
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" <Jo*******@HotMail.Com> wrote in message
news:uT**************@TK2MSFTNGP10.phx.gbl... It is no longer a useful discussion. I mean - I GGGGGGGGGAAAAAAAAVVVVVVVVVEEEEEE
UPPPPPPPP !!! OKKKKKKK!
John
Juan, you're just bad.
--
;-),
Kevin Spencer
Microsoft MVP
..Net Developer
I'd rather be a hammer than a nail.
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:uk**************@TK2MSFTNGP15.phx.gbl... 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" <Jo*******@HotMail.Com> wrote in message
news:uT**************@TK2MSFTNGP10.phx.gbl... It is no longer a useful discussion. I mean - I
GGGGGGGGGAAAAAAAAVVVVVVVVVEEEEEE UPPPPPPPP !!! OKKKKKKK!
John
Hi Juan
I think there has been a vast muddying of the waters in this thread
thanks for the clarification
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:eQ**************@tk2msftngp13.phx.gbl... 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/
======================================
"gerry" <ge**@hotmail.com> wrote in message
news:%2******************@tk2msftngp13.phx.gbl... 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
"Juan T. Llibre" <no***********@nowhere.com> wrote in message
news:Om**************@TK2MSFTNGP14.phx.gbl... re:
>All I care is Java Script is universal
You will have to live with, and die by, JavaScript, then.
re:
> then it should also work with the simple "required field" validator
component and I > should not have to code browsercaps mess.
But, it does work, as long as you identify the browser
and send it HTML/scripts it understands.
The whole "I shouldn't have to code" idea is just lazyness, to me.
I'm not saying that it should be harder/more complicated than
it needs to be, but requiring "no code" is just absurd.
That's how we make a living : by writing code!
Get used to it...or go to a different platform.
Then you''ll see what complex, *really hard to grasp* code is.
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" <Jo*******@HotMail.Com> wrote in message
news:%2******************@TK2MSFTNGP14.phx.gbl...
> "Juan T. Llibre" <no***********@nowhere.com> wrote in message
> news:%2*****************@TK2MSFTNGP15.phx.gbl...
>> re:
>>> A d/html page should be able to handle simple client side JS to
validate a "required >>> field" on any modern browsers (out of the box).
>>
>> How does a page validate anything client-side ?
>> Client-side validation requires a browser's interpretation.
>>
>> The server can validate a page server-side,
>> but the client-side validation must be made by the browser.
> All I care is Java Script is universal, and it has been working on
most modern browsers > that the current market offers. If it fails to validate a simple
"required field" > request on the client browser, then it is broken, incompatible,
considered as a bug, > monopoly, you name it. On top of that, if the same page can implement
onBlur and onFocus > events using the same script engine, then it should also work with
the simple "required > field" validator component and I should not have to code browsercaps
mess. >
> Why does it work on one and not the others ? Are Asp.Net Required
Field Validators using > different JS engine than onBlur, onFocus, onDoubleClick...? Why
should I have to > remember which one requires browsercap settings. That's bad design my
friend! NO GOOD!!! >
> John
4
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)
"Pat" wrote: its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
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
"StuntBeaver" <St*********@discussions.microsoft.com> wrote in message
news:F5**********************************@microsof t.com... 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)
"Pat" wrote:
its seems asp.net validation doesn't fire when using FireFox?
Tested a page and it doesn't fire.
It seems the javascript doesn't fire
Any ideas?
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: AnnMarie |
last post by:
My JavaScript Form Validation doesn't work at all in Netscape, but it
works fine in IE.
I made some of the suggested changes which enabled it to work in IE.
I couldn't make all the changes...
|
by: Brett Porter |
last post by:
Hi,
I have many, many forms that use all of the different form validation
controls. These work great on my local server however I have just been
alerted to the fact that the form validation...
|
by: Buddy Ackerman |
last post by:
I have one page where I used field validator controls and it works fine. It is set to do client side validation. I did the same thing on another page and set everything the same way as the first...
|
by: Jon Paal |
last post by:
validation doesn't fire
what's missing ?????
/////// ---- code -----///////////////////////////
Sub btnSubmit_Click(sender As Object, e As System.Web.UI.ImageClickEventArgs) 'Handles...
|
by: David Henderson |
last post by:
I know 'disable-output-escaping' has been discussed in the past, but I can't
put my finger on any of the threads to see if my current problem is
addressed. Sorry for re-asking the question if it...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
| |
