Hej!
Keryx webb skrev:
That's what we were discussing. If a page is sent as XHTML, one could
argue that it's supposed to be self-documenting, and that it might
mean that the xml-prologue should be more important than the
http-header. As my page proves, in FFox, MSIE and Opera (the three
I've
Keryx webb writes:
Andrew Cunningham wrote:
Keryx webb writes:
That's what we were discussing. If a page is sent as XHTML, one could
argue that it's supposed to be self-documenting, and that it might mean
that the xml-prologue should be more important than the http-header. As my
page
Andrew Cunningham wrote:
I was wondering if you should have another test in there: XHTML document
with no encoding declared in the http header or in a meta tag, and no
xml declaration. Sent as html/text.
That's text/html and an XHTML document served as text/html is HTML,
regardless of any
Keryx webb writes:
According to my tests Firefox *will* use the charset specified in the
http-header over the one in the XML-prologue if a page is sent as
application/xhtml+xml. (Or more exactly, regardless whether the page is
sent as text/html or application/xhtml+xml.) As will Opera.
