16728 2012-04-13 12:00:19 +0000 Blob.type 2012-05-07 06:46:54 +0000 1 1 1 Unclassified WebAppsWG File API unspecified PC All RESOLVED FIXED P2 normal --- 16950 1 zcorpan arun bzbarsky glenn public-webapps zcorpan public-webapps-bugzilla oldest_to_newest 66688 0 zcorpan 2012-04-13 12:00:19 +0000 "The ASCII-encoded string in lower case representing the media type of the Blob" DOMStrings aren't ASCII-encoded. If type was set with the Blob() constructor, it isn't necessarily in lowercase, either. 66692 1 glenn 2012-04-13 13:53:30 +0000 Is the intent for it to be restricted to the ASCII subset, and/or converted to lowercase in the ctor? 66771 2 arun 2012-04-17 19:57:29 +0000 I looked at RFC2046 and at the HTML5 specification, which 66772 3 arun 2012-04-17 19:59:32 +0000 *sigh Sorry for Comment 2; I submitted too soon. I looked at RFC2046 and at the HTML5 specification, which defines a valid MIME type string as matching RFC2616's media types section (3.7), to see if MIME type strings themselves are restricted to ASCII. They aren't as far as I can tell, and so we shouldn't have this requirement. 66773 4 bzbarsky 2012-04-17 20:14:30 +0000 RFC 2616 section 3.7 says: media-type = type "/" subtype *( ";" parameter ) type = token subtype = token Section 2.2 says: token = 1*<any CHAR except CTLs or separators> Section 2.2 says: CHAR = <any US-ASCII character (octets 0 - 127)> So MIME types are in fact restricted to ASCII. Furthermore, they're restricted to a subset of ASCII: "except CTLs or separators". 66774 5 arun 2012-04-17 20:44:39 +0000 So my first reading was right, which is why the requirement was there. But it's true that DOMStrings aren't ASCII-encoded. We may as well ignore this, and do what we do for invalid MIME types on the platform in general. Otherwise maybe we'd have to specify that: 1. Implementations throw if type is set with "invalid" non-ASCII chars 2. Specify that implementations do case conversion, if necessary. Don't know if we can really do those. 66775 6 bzbarsky 2012-04-17 21:17:06 +0000 > do what we do for invalid MIME types on the platform in general. It probably varies. At least some implementations, in some cases, byte-deflate and ASCII-lowercase. 66781 7 zcorpan 2012-04-18 07:02:55 +0000 We can do that in the Blob constructor and in Blob.slice (and anywhere else where Blobs are created with an author-specified MIME type). 67371 8 arun 2012-05-07 05:05:16 +0000 Marking this fixed. http://dev.w3.org/2006/webapi/FileAPI/#dfn-Blob