Forum Moderators: open

Message Too Old, No Replies

XHTML 1.0! but who misses out?

XHTML 1.0 Transitional pros and cons

         

kelownarealtors

4:02 am on Jan 12, 2005 (gmt 0)

10+ Year Member



Ok.

I have heard a lot of arguments for making your site XHTML validated. I switched my homepage (so far) over.

Because of this change, who am I excluding? Which browser versions would not be able to render this page properly or in error, and should I care?

Thanks
webmaster

<Sorry, no personal URLs. See TOS [webmasterworld.com]>

[edited by: tedster at 4:16 am (utc) on Jan. 12, 2005]

Hester

9:19 am on Jan 12, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Providing you've coded empty tags with a space before the end slash, no browsers should have a problem viewing your site. Also you will need to serve your pages as application 'text/html', which most people do. The only problems come when you go for complete strictness and serve XHTML as application xhtml/xml. While modern browsers like Opera and Firefox will cope with this, sadly IE6 cannot.

Otherwise, XHTML is more or less just the same as HTML. There are some areas of subtle difference though, but I don't think they will cause the page not to be displayed.

gmiller

8:46 am on Jan 18, 2005 (gmt 0)

10+ Year Member



XHTML served as text/html will simply be treated as mildly broken HTML by both old and new browsers. It doesn't buy you anything, but it doesn't do you any harm, either.

Ian Hickson ("Hixie" of Mozilla and Opera fame) wrote a pretty complete overview of the issues involved. A web search should turn it up.