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 18528 - Spec is unclear about the case sensitivity of parameter values
Summary: Spec is unclear about the case sensitivity of parameter values
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2012-08-10 16:11 UTC by Saurabh Anand
Modified: 2012-10-15 18:02 UTC (History)
2 users (show)

See Also:


Description Saurabh Anand 2012-08-10 16:11:29 UTC says that "Parameter values might or might not be case-sensitive,depending on the semantics of the parameter name".
Suppose, according to 4.B.b in I convert every character in relativeContentType to lower case, while the parameter value was in upper case or mixed case and was case sensitive under the current semantics of the parameter name, then this would be a violation of . is used in 4.B.c.

I feel that 4.B.b and 4.B.c can conflict with under the example I have given.

Expectation : Spec clearly defines the correct algorithm.
Comment 1 Arun 2012-10-15 18:02:25 UTC
We've decided to treat type as an opaque string.  Implementations don't throw; browser developers are reluctant to throw, and thus validation against the RFC is not useful.