Hello, on 03/21/2006 03:14 PM Norbert Wenzel said the following: > Manuel Lemos wrote: >> For instance, if you use method="post" because XHTML specification says >> everything should be in lower case, you will have problems with some >> browsers and e-mail programs that only accept POST in upper case and >> fallback to GET when they find something else. > > i would call that a problem of the browser, not of xhtml standards. You are missing the point. XHTML is not backwards compatible with HTML. If you assume otherwise you will run into browser incompatibility problems. It is irrelevant whether you can blame it on the browser or not. If you use XHTML where HTML would have worked perfectly, Web site users do not want to know if you are using the latest and the greatest markup specification. What they know is that your site will not work properly in their browser of choice and you may have to deal with non-technical problems because of a bad technical decision which is to jump blindly to using the latest and the greatest new new thing. The same could be said about using CSS based layouts versus tables or XMLHttpRequest versus IFRAME. -- Regards, Manuel Lemos Metastorage - Data object relational mapping layer generator http://www.metastorage.net/ PHP Classes - Free ready to use OOP components written in PHP http://www.phpclasses.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
