XHTML 1.1 is impossible with ASP.NET 2.0?

[Cat]

I created a web site, and I thought I followed XHTML 1.1 rules. But
when I validated the pages, I got some error messages. I found that
those codes are automatically generated parts by ASP.NET.

There is no attribute "name".
<form name="form1" method="post" action="Default .aspx" id="form1">
And input is not allowed here

Since ASP.NET buttons should be placed in server side forms, I don't
know how to remove this error. So, what this comes down to is that it
is (normally) impossible to create XHTML 1.1 page with ASP.NET 2.0? I
tried to search the internet but all I found was to create a hacked
assembly and place it on the server. But this is impossible since I'm
not the administrator of my hosting provider's computer. Is there any
normal way to suppress the generation of name tag and hidden input
tag? Or should I not use XHTML 1.1 with ASP.NET 2.0?

Thank you.

[bruce barker]

there is no xhtml 1.1 browser, so some compromise is necessary. to
access the form the asp.net client code uses document.forms[name]
syntax, so a name attribute is required. if only uplevel support was
needed they could switch to document.getEle mentById, but the basic code
supports older browsers that do not support document.getEle mentByName.

xhtml 1.1 does support <input type="hidden">, so I don't know what your
trouble is.
-- bruce (sqlwork.com)

Cat wrote:

I created a web site, and I thought I followed XHTML 1.1 rules. But
when I validated the pages, I got some error messages. I found that
those codes are automatically generated parts by ASP.NET.

There is no attribute "name".
<form name="form1" method="post" action="Default .aspx" id="form1">
And input is not allowed here

Since ASP.NET buttons should be placed in server side forms, I don't
know how to remove this error. So, what this comes down to is that it
is (normally) impossible to create XHTML 1.1 page with ASP.NET 2.0? I
tried to search the internet but all I found was to create a hacked
assembly and place it on the server. But this is impossible since I'm
not the administrator of my hosting provider's computer. Is there any
normal way to suppress the generation of name tag and hidden input
tag? Or should I not use XHTML 1.1 with ASP.NET 2.0?

Thank you.

[Patrice]

For this particular point try :
http://msdn2.microsoft.com/en-us/library/ms178159.aspx
(AFAIK this is not an XHTML 1.1 issue).

What is the XHTML 1.1 feature you need (I don't really know myself whay it
offers) ? If none, I would stick to XHTML 1.0 (possibly strict)

"Cat" <ty*******@gmai l.coma écrit dans le message de news:
11************* *********@a75g2 00...legr oups.com...

>I created a web site, and I thought I followed XHTML 1.1 rules. But
when I validated the pages, I got some error messages. I found that
those codes are automatically generated parts by ASP.NET.

There is no attribute "name".
<form name="form1" method="post" action="Default .aspx" id="form1">
And input is not allowed here

Since ASP.NET buttons should be placed in server side forms, I don't
know how to remove this error. So, what this comes down to is that it
is (normally) impossible to create XHTML 1.1 page with ASP.NET 2.0? I
tried to search the internet but all I found was to create a hacked
assembly and place it on the server. But this is impossible since I'm
not the administrator of my hosting provider's computer. Is there any
normal way to suppress the generation of name tag and hidden input
tag? Or should I not use XHTML 1.1 with ASP.NET 2.0?

Thank you.