Closed GoogleCodeExporter closed 9 years ago
The "correct" fix is to use content negotiation to determine the mime type to
use.
However, this is fiddly to set up. Alternatively, we can use the user agent to
serve
a different mime type to IE, but this is fragile (breaks for browsers which
"wrap"
the IE HTML component, but send a different user-agent string, for example).
An alternative fix is just to serve all our pages as HTML rather than XHTML. I
think
this might be the way to go for 1.0, since it's the easy fix.
Original comment by boulton.rj@gmail.com
on 29 Oct 2007 at 11:27
Actually, we're already serving our pages as text/html; I wonder if the problem
is
the leading <?xml declaration.
Original comment by boulton.rj@gmail.com
on 29 Oct 2007 at 11:27
Original comment by paul.x.r...@googlemail.com
on 29 Oct 2007 at 11:59
Original issue reported on code.google.com by
paul.x.r...@googlemail.com
on 29 Oct 2007 at 10:34