I don't believe having a class attribute on a td element would cause that
error. In fact, since when is a class attribute not allow on a td element??
Actually, you can apply any attribute you can dream up to an element. VS
may put the red squiggle line under it, but it won't cause the error your
seeing or prevent your code from running. You sure you have a well-formed
document? No mismatched tags?
Greg
"Paul Darroch" <po******@sweeney-kincaid.co.uk> wrote in message
news:uI**************@TK2MSFTNGP12.phx.gbl...
Hi
It is my every intention to rewrite the site, employing "proper" ASP.NEt
code and approaches; however, I need a quick way to migrate the existing
code to valid ASP.Net so that I can share session data, etc and so allow
me to rewrite the site in "proper" ASP.Net. It is for this reason that I
am looking to stop these errors, as I simply don't care whether or not a
td element should or should not contain a class attribute! Is there any
way of stopping these errors from occurring?
What did you mean by "The client-side controls have a few gaps in the
schema..."? Does this mean I can alter the schema used to determine what
elements can contain what attributes, etc?
Thanks
PD
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!