<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1040253" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1040253</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/html-css-and-javascript/why-using-texthtml-xhtml-bad#comment-1226901</link>
    <description> &lt;p&gt;An interesting topic, yes. An old one, as well !&lt;/p&gt;
&lt;p&gt;Harmful or not, I&#039;d guess some 99% or more &quot;webmasters&quot; have no idea that their lovely XHTML code is interpreted as HTML by every browser on earth, with no benefit from all the XML goodness promised by XHTML evangelists.&lt;/p&gt;
&lt;p&gt;It has to do with MIME types. While the file name ends in .htm, .html, ,php, or similar, nearly every host will send the document as MIME type text/html. The .php does not work from a hard drive, but the usual setup for files on the hard drive treats .htm and .html as MIME type text/html as well. Not a trace of &quot;eXtensible&quot; markup anywhere.&lt;/p&gt;
&lt;p&gt;Generally speaking, but not universally true, if you add the &amp;lt;?xml declaration to the beginning of your validating XHTML document, then rename it with a .xhtml extension, it is likely that it will be treated as genuine XHTML. Not guaranteed, but worth a try.&lt;/p&gt;
&lt;p&gt;Any road up, (mis)using XHTML markup as faux HTML has not broken the web yet. I think that Hickson rather overstates his case.&lt;/p&gt;
&lt;p&gt;Anyone out there with another experience / point of view?&lt;/p&gt;
 </description>
     <pubDate>Sat, 01 Dec 2007 02:49:28 +0000</pubDate>
 <dc:creator>webwiz</dc:creator>
 <guid isPermaLink="false">comment 1226901 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
