23106 2013-08-30 19:41:18 +0000 Spec should treat content type as an opaque string 2013-09-04 18:12:13 +0000 1 1 1 Unclassified WebAppsWG File API unspecified All All RESOLVED INVALID P2 normal --- 1 Ms2ger arun annevk public-webapps public-webapps-bugzilla oldest_to_newest 92761 0 Ms2ger 2013-08-30 19:41:18 +0000 Bug 18521, bug 18523, bug 18528 and bug 18529 claim: > We've decided to treat type as an opaque string. However, the Blob constructor [1] and the slice method [2] still lower-case their argument and limit it to the U+0020-U+007E range. This seems inconsistent. [1] http://dev.w3.org/2006/webapi/FileAPI/#constructorBlob [2] http://dev.w3.org/2006/webapi/FileAPI/#dfn-slice 92847 1 annevk 2013-09-03 09:41:27 +0000 I'm pretty sure that's because we changed our mind. The question is where we should put the constraints and what conversion between code units and bytes we should make. It cannot be a code unit sequence without conversion algorithm to bytes. Making it a ByteString would make some sense... 92879 2 arun 2013-09-03 14:00:05 +0000 Ms2ger: In fact, it's not an inconsistency so much as a compromise. Sticking to rigid parsing of type would bind us to specs that are themselves inconsistent (but I treat http://mimesniff.spec.whatwg.org/ as normative these days). Anne: OK, I've logged Bug 23138. 92994 3 arun 2013-09-04 17:57:15 +0000 Since Bug 23138 was logged, I think this can be marked INVALID. Bug 23138 brings an IDL change, and some prose change about code points.