9525 2010-04-15 08:09:32 +0000 WHat happens when a browser supports both XHTML and HTML? Which has precedence? There should be a decision chart leading to this point with defaults for missing elements then something to say what you use if you support both and the Web page is missing w 2010-10-04 14:56:28 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#interactive P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35058 0 contributor 2010-04-15 08:09:32 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#interactive Comment: WHat happens when a browser supports both XHTML and HTML? Which has precedence? There should be a decision chart leading to this point with defaults for missing elements then something to say what you use if you support both and the Web page is missing whatever would make the decision earlier. Posted from: 124.189.67.244 35065 1 ian 2010-04-15 08:36:16 +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: I don't understand. What decision is there to make? Doesn't the spec already define that the MIME type is what you base the decision on?