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 8899 - 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"
Summary: it should define how to parse or compare mime types because http spec does no...
Status: RESOLVED NEEDSINFO
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-02-07 12:19 UTC by contributor
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-02-07 12:19:56 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-02-14 10:44:00 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: 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.)