This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9289 - 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.
Summary: What about polyglot documents which are *both* HTML5 and XHTML5 ? I think it ...
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-22 14:56 UTC by contributor
Modified: 2010-10-04 14:00 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-03-22 14:56:58 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-03-31 21:02:13 UTC 
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?
Comment 2 Andreas Kuckartz 2010-04-09 12:03:41 UTC 
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.
Comment 3 Ian 'Hixie' Hickson 2010-04-13 07:31:25 UTC 
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.
Comment 4 Andreas Kuckartz 2010-04-13 07:48:00 UTC 
That implies that XHTML5 is already dead.
Comment 5 Andreas Kuckartz 2010-06-28 08:14:15 UTC 
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.