On Sat, Sep 4, 2010 at 14:46, Jeremy Shaw
So the choices are:
1. only focus on getting the xhtml 1.0 served as application/xml working correctly, and ie users get nothing..
2. create xhtml 1.0 that would work correctly if served as application/xml, but serve it as text/html, and ignore that fact that some stuff might not be rendering correctly when treated as text/html.
3. create xhtml documents which render correctly whether served as application/xml or text/html, but then only serve them as text/html anyway
4. forget about how the xhtml documents render as application/xml, and only focus on how they render as text/html.
5. Do as my patch does; default to HTML 4 (supported by all browsers), and allow users to generate correct XHTML if they want/need to.