- From: <bugzilla@jessica.w3.org>
- Date: Thu, 03 Mar 2011 21:28:01 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11909 Eliot Graff <eliotgra@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #16 from Eliot Graff <eliotgra@microsoft.com> 2011-03-03 21:27:56 UTC --- The part of the Introduction that contains the principles of polyglot now reads as follows in the 3 March Editor's Draft: ]] Polyglot markup results in: • a valid HTML document. [HTML5] • a well-formed XML document. [XML10] • identical DOMs when processed as HTML and when processed as XML. A noteable exception to this is that HTML and XML parsers generate different DOMs for some xml (xml:lang, xml:space, and xml:base), xmlns (xmlns="" and xmlns:xlink=""), and xlink (such as xlink:href) attributes. XML requires and HTML5 permits these attributes in certain locations and the attributes are preserved by HTML parsers. Polyglot markup is not constrained: • to be valid XML. [XML10] • by conformance to any XML DTD. Polyglot markup is scripted according to the rules of XML (does not use document.write, for example) and excludes HTML elements that are impossible to replicate in an XML parser (does not use the <noscript> element, for example). Polyglot markup triggers non-quirks mode in HTML parsers, as non-quirks mode is closest to XML-mode rendering, in regard to both DOM and CSS. Polyglot markup results in the same encoding and the same language in both HTML-mode and XML-mode. [[ I think that this covers the requests below. Thanks, once more, for your help! Eliot -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 3 March 2011 21:28:02 UTC