Turning off client-side validation

Oleg Kolpashchikov · July 8th, 2013, 07:44 PM

Chapter 6, page 224-225

"Turning off client-side validation"

This section does not mention a possibility to turn off client scripts with a single attribute in the Page-directive:

<@ Page ClientTarget="downlevel"

It seems to be easier and faster than writing

Code:

foreach (BaseValidator bv in Page.Validators)
{   bv.EnableClientScript = false;   }

Is it considered to be a bad practice to use "ClientTarget"-attribute?

MSDN:
http://msdn.microsoft.com/en-us/libr...enttarget.aspx

Imar · July 9th, 2013, 11:21 AM

Hi there,

That settings turns off more than just client side validation. With that setting on, ASP.NET assumes the browser doesn't support JavaScript and will use scriptless version of other control and content as well: http://msdn.microsoft.com/en-us/libr...enttarget.aspx

I wouldn't recommend using it just to turn off client side validation.

Cheers,

Imar

Oleg Kolpashchikov · July 9th, 2013, 03:25 PM

That's a good point - other controls that normally would be rendered with JS - will be rendered differently.
I'll do some testing for myself to clarify it.

Thanks!

Oleg Kolpashchikov · July 10th, 2013, 09:43 PM

UpdatePanel does not work properly with ClientTarget="downlevel" - it does a postback every time I change something inside it, like change a date on the calendar.

"Normal"-version brings in 3 JS-files, "downlevel" version only 1 JS-file (ASP.NET AJAX)

Imar · July 11th, 2013, 02:23 AM

Exactly; ASP.NET assumes this downlevel browser doesn't support it. While it still renders some JavaScript, I don't know.

Cheers,

Imar