Keryx webb wrote:
3. If not (2): If the content is (X)HTML, UAs use the meta-tagg. When loading pages from local files or from an FTP-server, where obviusly no HTTP-headers are sent, this is what the browser should use to get the encoding.
Meta elements are *not* used in XHTML files at all, this only applies to HTML. But this needs to be clarified that XHTML served as text/html *is* HTML, regardless of what the DOCTYPE says.
Value of declaratons: HTTP-headers > XML-prologue > Meta-tags
It's not quite as simple as that. It's more like this: for text/html: HTTP headers --> <meta> element --> content-sniffing for application/xml and */*+xml (excluding text/*) HTTP headers --> XML Declaration --> BOM (UTF-8 or UTF-16 LE/BE) for text/xml HTTP headers --> US-ASCII (XML declaration is ignored)
MSIE-values: It's own "judgement" > HTTP-headers > XML-prologue > Meta-tags
Again, it's not quite as simple as that. For text/html, the XML declaration is *not* used at all, IE doesn't even understand it and triggers quirks mode if it's present.
IE supports application/xml and text/xml and it will respect the XML declaration, but I'm not sure how standards compliant it's behaviour is with regard to encoding detection in XML.
I'm not aware of any case where IE will override the character encoding in the HTTP headers, only the MIME type. Can you provide a demonstration or provide a link to some documentation of the bug?
-- Lachlan Hunt http://lachy.id.au/ ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
