Quirks mode

leo,

If you search the forum for xhtmlConformance mode not set to "Strict" and AJAX problems, you'll get and idea of the issues you may have using non xhtml compliant code with AJAX.

And I think you are wrong when you say "I NEED to use quirks for IE6". In my experience, you can produce XHTML 1.0 strict valid pages for IE6, you just need to work harder on the CSS department. Even more, except for a very few controls, I can almost validate my website as XHTML 1.1 Strict, and I develop with IE6 in mind, like everyone else does.
Just as an idea, it helped me a lot the use of the ASP.NET CSS Friendly control adapters.

Regards,

Juan

Rasetti, thanks for your reply.

I have a very specific scenario, where I am using webparts and it's a nightmare to have this working in standards mode, because I need 100% table heights so the webparts can move OK across webpart zones. I tried to design a page in standards mode but it didn't work as expected. So I have it running in quirks mode for IE6 and standards mode for Firefox. If I could use only firefox it would be excelent, but I can't .

I know some toolkit controls have problems when working in quirks mode, like the Modal Popup. But there are also fixes to make it work, like this one:

http://www.codeplex.com/AtlasControlToolkit/WorkItem/View.aspx?WorkItemId=8150

So I just think the toolkit developers should clearly say, for each one of the controls, which works in quirks mode and which don't work. We could have this in the documentation or the Codeplex website.

I know some controls work no matter you are in quirks mode and standards mode. For example: the cascading drop down list.

So instead of saying "we don't support quirks mode" they should be specific about each control. It would be more friendly and useful to us developers.

Just a suggestion.

Cheers