9289 2010-03-22 14:56:58 +0000 What about polyglot documents which are *both* HTML5 and XHTML5 ? I think it would make a lot of sense to spend a few words on that because virtually nobody will use XHMTL5 with the correct MIME-type because of the legacy browsers. 2010-10-04 14:00:03 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other CLOSED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-xhtml-syntax P3 normal LC 1 contributor ian a.kuckartz ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 33747 0 contributor 2010-03-22 14:56:58 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-xhtml-syntax Comment: What about polyglot documents which are *both* HTML5 and XHTML5 ? I think it would make a lot of sense to spend a few words on that because virtually nobody will use XHMTL5 with the correct MIME-type because of the legacy browsers. Posted from: 217.91.15.219 34270 1 ian 2010-03-31 21:02:13 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Did Not Understand Request Change Description: no spec change Rationale: What exactly do you suggest should be said? 34703 2 a.kuckartz 2010-04-09 12:03:41 +0000 Additional info: What precisely are the requirements if I want to be able to deliver one and the same page as either XHTML5 or HTML5 when the code of both "versions" should be identical and only the MIME-type is different? While it should be possible to find those requirements by reading the complete specification it would be easier if that info were available at one place. 34878 3 ian 2010-04-13 07:31:25 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: The answer is long and complicated, involving many things outside of HTML, for example being using DOM APIs in particular ways, using CSS selectors in particular ways, etc. I really don't think we want to document this in the spec. Doing so would only encourage people to do it. 34887 4 a.kuckartz 2010-04-13 07:48:00 +0000 That implies that XHTML5 is already dead. 36443 5 a.kuckartz 2010-06-28 08:14:15 +0000 For those stumbling upon this entry. A draft of a W3C document exists which tries to answer my question in detail: Polyglot Markup: HTML-Compatible XHTML Documents W3C Editor's Draft 24 June 2010 http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html I therefore changed the status of this entry to closed / fixed.