23431 2013-10-03 14:35:55 +0000 File API should say what to do with the query string in blob: URLs 2013-11-17 00:01:05 +0000 1 1 1 Unclassified WebAppsWG File API unspecified PC All RESOLVED FIXED P2 normal --- 1 arun arun annevk glenn public-webapps public-webapps-bugzilla oldest_to_newest 94231 0 arun 2013-10-03 14:35:55 +0000 Currently, the File API mentions what can be done with the fragment identifier, but doesn't say anything about the query string. The File API should mention that blob: URLs should explicitly ignore the query string. 94654 1 annevk 2013-10-14 13:25:32 +0000 Should we at some point move all this logic to Fetch? I.e. you define how to create the URL, Fetch defines how to obtain from a blob URL? Or should Fetch provide a hook for your specification? 94658 2 arun 2013-10-14 15:05:17 +0000 One "pro" of moving everything to Fetch would be to have a central place to accommodate all the (proliferating) schemes. For instance, File API defines request-response behavior for the blob: scheme, much of which is reproduced in mediastream: URLs. Then, the FileSystem API will define the filesystem: scheme, which is currently implemented in Chrome, and which the specification will standardize. If all of it is routed via Fetch, we'll have a single normative source for URL dereferencing. But I'm not *strongly* opinionated on this, and don't mind the solution of it living in separate specifications. For "LC" purposes, the File API will define blob: and maybe successor drafts (including Fetch) can deal with the protocol as it evolves (hopefully not too much). 95642 3 arun 2013-10-31 22:37:11 +0000 Fixed. http://dev.w3.org/2006/webapi/FileAPI/#queryString 95652 4 glenn 2013-11-01 02:34:31 +0000 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). 95669 5 annevk 2013-11-01 11:44:57 +0000 Indeed, the way to fix this is to define blob URLs in terms of http://url.spec.whatwg.org/ and not in ABNF as that will not be used for parsing them anyway once http://url.spec.whatwg.org/ is implemented. 95699 6 arun 2013-11-01 17:36:18 +0000 (In reply to Glenn Maynard from comment #4) > 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). I agree with this comment, and have changed the spec. to reflect this feedback. 95700 7 arun 2013-11-01 17:37:53 +0000 (In reply to Anne from comment #5) > Indeed, the way to fix this is to define blob URLs in terms of > http://url.spec.whatwg.org/ and not in ABNF as that will not be used for > parsing them anyway once http://url.spec.whatwg.org/ is implemented. I think reworking this for blob: isn't useful, since it's a simple enough scheme without any real components. But url.spec.whatwg.org will be what the filesystem: scheme should be defined based on. 95701 8 annevk 2013-11-01 17:41:43 +0000 Arun, all URLs should be defined and created equal. There's only one URL parser after all. 95830 9 arun 2013-11-05 21:09:44 +0000 (In reply to Anne from comment #8) > Arun, all URLs should be defined and created equal. There's only one URL > parser after all. Yes, but blob: is already in implementations and shipping, and I'm not clear exactly what you're suggesting. We already defer to fetch for parts of blob: URL ref culling. So: 1. Are you suggesting that url.spec.whatwg.org adds other schemes to the existing scheme list in Section 5 (that is, http://url.spec.whatwg.org/#urls)? If so, I support that, and think you may as well add some riders such as mediastream:, which ought to behave exactly like blob: as far as schemes go, since mediastream: is essentially blob: by another name. Then, when that becomes authoritative, we should deprecate what I have in the File API (which itself may be deprecated by any specs that emerge out of the ongoing discussion about Streams). 2. Or, are you suggesting I rewrite the blob: definition in terms of url.spec.whatwg.org in the File API spec.? That would have been useful feedback a bit earlier in the game. I'm not totally sure what it buys us now. Implementations are still free to use "one URL parser." 95856 10 annevk 2013-11-06 10:41:17 +0000 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.) 96412 11 arun 2013-11-17 00:01:05 +0000 (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.