[Bug 23431] File API should say what to do with the query string in blob: URLs
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23431 Arun a...@mozilla.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Arun a...@mozilla.com --- (In reply to Anne from comment #10) I don't think you understand. The URL Standard already defines parsing for all URLs. Relative schemes are treated specially, but for all other schemes the URL ends up as scheme, scheme data, query, and fragment. To define blob URLs in terms of this you just have to say what the scheme data can be (if you want to restrict the code points for producers), maybe that a conforming blob URL does not have a query and that fragment can be anything. (Reworded in specification prose of course.) OK, fixed per your suggestions. http://dev.w3.org/2006/webapi/FileAPI/#DefinitionOfScheme Reopen if necessary. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 23431] File API should say what to do with the query string in blob: URLs
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23431 Arun a...@mozilla.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Arun a...@mozilla.com --- Fixed. http://dev.w3.org/2006/webapi/FileAPI/#queryString -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 23431] File API should say what to do with the query string in blob: URLs
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23431 Glenn Maynard gl...@zewt.org changed: What|Removed |Added Status|RESOLVED|REOPENED CC||gl...@zewt.org Resolution|FIXED |--- --- Comment #4 from Glenn Maynard gl...@zewt.org --- I don't think it needs to say anything. Specs say what to do, not what not to do; if it doesn't say to do anything with the query parameter, then nothing is done with the query parameter. The language now in the spec is confusing: it doesn't clearly mean anything, and might be interpreted to mean something wrong. For example, if you parse a blob URL with new URL(blobURL), clearly the .search attribute of the result should include the query, even if it's a blob URL. The vague language must ignore a query string might be interpreted to contradict that, as if the file API spec is implicitly monkey-patching the URL spec. If the intent is to ensure that appending ?foo to a blob URL doesn't affect resolving the resource, then you probably just want to define which parts of the parsed URL are the unique identifier. With the URL spec's terminology, it looks like the identifying part is the scheme data (which doesn't include the query or the fragment). -- You are receiving this mail because: You are on the CC list for the bug.
