| 155 | The page we are editing may be in XHTML but it is delivered as text/html and thus processed as "tag soup". See the following links for details of why XHTML is problematical: |
| 156 | http://friendlybit.com/html/why-xhtml-is-a-bad-idea/ |
| 157 | http://hixie.ch/advocacy/xhtml -- sending xhtml as text/html considered harmful |
| 158 | |
| 159 | As far as market share is concerned - see http://marketshare.hits |
| 160 | They quote IE 6 as still having a 25% market share - installed base will be higher as many using Firefox will not have updated it. |
| 161 | |
| 162 | Even if XHTML worked with other MS browsers, we should not generate content which is unreadable by a quarter of the web population. |
| 163 | |
| 164 | The only justification for using XHTML is embedded MathML or SVG, etc, but I don't think that applies to our pages. Often one could embed the extra content in an iframe in any case... --MichaelRoberts |