8899 2010-02-07 12:19:56 +0000 it should define how to parse or compare mime types because http spec does not define it but html UAs have to know how to treat invalid input such as type="text/css; incomplete-parameter" 2010-10-04 14:46:49 +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/#valid-mime-type P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31620 0 contributor 2010-02-07 12:19:56 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#valid-mime-type Comment: it should define how to parse or compare mime types because http spec does not define it but html UAs have to know how to treat invalid input such as type="text/css; incomplete-parameter" Posted from: 220.210.139.122 32052 1 ian 2010-02-14 10:44:00 +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: Is there a specific case where MIME types are used where this is not defined? (There may be, it wasn't immediately obvious to me. I know for a number of cases, e.g. getting the character encoding information, the spec defines how to parse the MIME type explicitly.)