The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

While those ASP.NET client-side validation routines make some use of the W3C DOM, some of them also rely on IE-specific DOM features such as .innerText, and IE's Event model. So they're not all going to work in other browsers.

"some of them also rely on IE-specific DOM features such as .innerText, and IE's Event model. So they're not all going to work in other browsers."

^ ^ ^

I read the above as ".NET doesn't know the difference, and if you aren't careful will send tags to Netscape that it doesn't know what to do with", which is in fact untrue. It will only send IE-specific tags to IE. It's the way in which ASP.NET controls are programmed.

For instance, the calendar control. For IE, it displays an amazingly fully functional piece of JS/CSS which does in fact use proprietary tags.

For NS, it does the same thing, with different scripting.

For older versions of IE, it just uses CSS and some lighter JS.

For other browsers, it displays links, which allow you to mimick the functionality by navigating to different pages.

Then again, maybe I'm just reading his statement wrong. Basically, in order to send the wrong tags to the wrong browser, the developer would need to purposefully code in "for [x] browser, use wrong tags"

I read the above as ".NET doesn't know the difference, and if you aren't careful will send tags to Netscape that it doesn't know what to do with", which is in fact untrue. It will only send IE-specific tags to IE. It's the way in which ASP.NET controls are programmed.

So why are some of the samples linked above sending code using document.all to mozilla?