- From: <bugzilla@jessica.w3.org>
- Date: Mon, 27 May 2013 09:13:25 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21818 Robin Berjon <robin@w3.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robin@w3.org --- Comment #5 from Robin Berjon <robin@w3.org> --- Trying to make this actionable, if we look inside http://www.w3.org/html/wg/drafts/html/master/document-metadata.html#attr-meta-http-equiv-content-type we currently have: """ <p> The Encoding declaration state may be used in HTML documents, but elements with an http-equiv attribute in that state must not be used in XML documents. </p> """ So the proposal would be to replace that with: """ <p> The Encoding declaration state may be used in HTML documents and in XML documents. If the Encoding declaration state is used in an XML document, the name of the character encoding must be an ASCII case-insensitive match for the string "UTF-8" (and the document is therefore forced to use UTF-8 as its encoding). </p> <p class=note> The Encoding declaration state has no effect in XML documents, and is only allowed in order to facilitate migration to and from XHTML. </p> """ Is that correct? Would it address your concerns? Has anyone checked implementations on this? I don't mind making this change so long as browsers *really* ignore this instruction in XHTML. A test case would be most valuable. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 27 May 2013 09:13:34 UTC