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 24745 - "Parse a MIME type" algorithm compares bytes to code points
Summary: "Parse a MIME type" algorithm compares bytes to code points
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: MIME (show other bugs)
Version: unspecified
Hardware: All All
: P2 minor
Target Milestone: Unsorted
Assignee: Gordon P. Hemsley
QA Contact: sideshowbarker+mimespec
URL: http://mimesniff.spec.whatwg.org/#par...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-20 13:30 UTC by Gordon P. Hemsley
Modified: 2019-03-29 22:39 UTC (History)
3 users (show)

See Also:

Attachments

Description Gordon P. Hemsley 2014-02-20 13:30:04 UTC 
Per zcorpan, the "parse a MIME type" compares bytes to code points.

Presumably this algorithm should be analyzing only the raw (though ASCII-like) byte stream, and so should refer to ASCII bytes (0xNN) instead of Unicode code points (U+NNNN).
Comment 1 Simon Pieters 2014-02-24 10:03:33 UTC 
Doesn't this need to be invoked from places where you have a string instead of a stream of bytes, e.g. video.canPlayType?
Comment 2 Gordon P. Hemsley 2014-02-24 13:32:51 UTC 
(In reply to Simon Pieters from comment #1)
> Doesn't this need to be invoked from places where you have a string instead
> of a stream of bytes, e.g. video.canPlayType?

I think the jury's still out on that; is that dependent on bug 11984?
Comment 3 Domenic Denicola 2019-03-29 22:39:19 UTC 
Parse a MIME type got rewritten and is now good on this front.