Tackling non-standards compliance in asp.net 1.1

A lot of large organisations still use .net 1.1 and subsequently asp.net 1.1 because of processes, software packaging etc.

In these rock 'n' roll standards compliant days of the web, a fundamental problem remains. Asp.net 1.1 likes to use proprietry attributes (such as script language="javascript" as opposed to type="text/javascript"). This means your asp.net 1.1 web application fails in some standards compliancy isuues, namely proprietry attributes in your markup.

Using some fancy DOM Scripting may be one way of removing unwanted attributes and inserting the right ones, but surely that's just holding your hand up and saying "I know its dirty markup, so I'm going to brush the dirt under the rug and pretend it was ok all along". Trouble is, with a little searching, clients can uncover the "dirt from beneath the rug".

How else are you going to remove the proprietry "language" attribute from the postback event?