D
danny.rendle
I am attempting to create a web site using ASP.NET v1.1 to comply with
the W3C's WAI Triple-A standard.
To this end I need ASP.NET to emit valid HTML 4.01 Transitional (once
confident with ASP.NET and HTML 4.01 I plan to move onto XHTML).
I have found several articles suggesting the use of Response Filters to
amend the HTML on route to the client which are very usefull for adding
a container for the ViewState and removing the Form's name attribute.
My problem is that when using Validator Controls to perform Client (and
Server Side) validation, for the Validators to work client side, they
must be accompanied by a hidden HTML span with multiple attributes.
E.g. <span id="ucClient_rfvFirstName"
controltovalidate="ucClient_txtFirstName" errormessage="First Name"
display="None"
evaluationfunction="RequiredFieldValidatorEvaluateIsValid"
initialvalue="" style="color:Red;display:none;"></span>
These additional attributes cause the markup to fail validation as they
are not part of the HTML 4.01 Transitional DTD.
Can anybody tell me how to make an ASP.NET page that uses Validator
Controls validate against the HTML 4.01 DTD?
Will I, as I currently fear, have to resort to Server Side validation
only?
the W3C's WAI Triple-A standard.
To this end I need ASP.NET to emit valid HTML 4.01 Transitional (once
confident with ASP.NET and HTML 4.01 I plan to move onto XHTML).
I have found several articles suggesting the use of Response Filters to
amend the HTML on route to the client which are very usefull for adding
a container for the ViewState and removing the Form's name attribute.
My problem is that when using Validator Controls to perform Client (and
Server Side) validation, for the Validators to work client side, they
must be accompanied by a hidden HTML span with multiple attributes.
E.g. <span id="ucClient_rfvFirstName"
controltovalidate="ucClient_txtFirstName" errormessage="First Name"
display="None"
evaluationfunction="RequiredFieldValidatorEvaluateIsValid"
initialvalue="" style="color:Red;display:none;"></span>
These additional attributes cause the markup to fail validation as they
are not part of the HTML 4.01 Transitional DTD.
Can anybody tell me how to make an ASP.NET page that uses Validator
Controls validate against the HTML 4.01 DTD?
Will I, as I currently fear, have to resort to Server Side validation
only?