- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 Nov 2012 21:54:35 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19923 Eliot Graff <eliotgra@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #6 from Eliot Graff <eliotgra@microsoft.com> --- Thank you for your comments here and in the mail threads. I appreciate the time and effort that you put in this. I do not see, however, substantively new or different information here than in bug 9969 and bug 12725, both of which raise the same issue. My response in those instances was this: After lengthy and careful consideration, I am going to resolve this as won't fix for the following reasons. "Polyglot Markup: HTML-Compatible XHTML Documents" is a normative specification that defines and prescribes behavior for "polyglot markup," as defined within that specification. However, because there are no consequences to user agents, only to authors (not having the same DOM and not creating content that validates as either HTML5 or XML), I have consciously removed any RFC 2119 language, UNLESS it is required by an original normative specification. Regarding the other issue in comment 1: as many other specifications do, the polyglot spec relies upon some definitions that come from other normative specifications. When and if the references within the polyglot spec are in error or mis-quote the original spec, a bug should be logged against the polyglot specification to that extent, and as editor, I will make corrections as quickly as possible. Thank you for your patience and your input. Eliot *** This bug has been marked as a duplicate of bug 9969 *** -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 12 November 2012 21:54:36 UTC