[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #29 from Arun --- (In reply to Anne from comment #28) > Don't check for "parse error", see if the algorithm returns failure. Done! > Also, it may not return a host or port. You should probably check if it's a > relative scheme. It's true that it could be a relative scheme, so I check for a relative scheme per your advice. But, it will never be a relative URL; that is, the recursive invocation of the basic URL parser will never also be fed a base URL. So, host will always be extractable, since the emitter methods (URL.createFor and URL.createObjectURL) will always emit a full origin string, namely the effective script origin specified by the settings object. > > I think you probably just want to parse it and then say something like > "return /parsedURL/'s origin". Done! > But maybe I should just bite the bullet and define origin for all URL > schemes we care about. If you do this, some portions of this in File API might be made redundant. We've already made the section on request-response informative; other sections may follow suit. Please give it a check: http://dev.w3.org/2006/webapi/FileAPI/#extractionOfOriginFromIdentifier -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Anne changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #28 from Anne --- Don't check for "parse error", see if the algorithm returns failure. Also, it may not return a host or port. You should probably check if it's a relative scheme. I think you probably just want to parse it and then say something like "return /parsedURL/'s origin". But maybe I should just bite the bullet and define origin for all URL schemes we care about. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #27 from Arun --- (In reply to Anne from comment #24) > You don't need to define 1. That is already handled by the generic URL > parser. Done per http://dev.w3.org/2006/webapi/FileAPI/#extractionOfOriginFromIdentifier -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Anne changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #7 from Anne --- This is wrong. The URL parser is http://url.spec.whatwg.org/ That returns you components you can operate on. 'scheme data' seems to be the identifier you want. Or maybe 'scheme data' + "?" + 'query'. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Arun changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Arun --- (In reply to Anne from comment #5) > This algorithm should operate on a parsed URL, not a fresh URL. You want to > hand this algorithm a scheme data component. Done! And revisited the original intent of this bug. So: 1. Specified extracting the identifier from a fresh URL: http://dev.w3.org/2006/webapi/FileAPI/#extractionOfIdentifierFromBlobURL 2. Specified extracting origin from a scheme data component / identifier: http://dev.w3.org/2006/webapi/FileAPI/#extractionOfOriginFromIdentifier Clarified what emitting methods do. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Anne changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Anne --- This algorithm should operate on a parsed URL, not a fresh URL. You want to hand this algorithm a scheme data component. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 25914] No definition of parsing blob's scheme data
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914 Arun changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Arun --- (In reply to Anne from comment #3) > If we use scheme data as identifier, fine. > > Yes, I'd like a way to extract an origin out of the scheme data. OK, I think http://dev.w3.org/2006/webapi/FileAPI/#extractionOfOriginFromBlobURL will work. -- You are receiving this mail because: You are on the CC list for the bug.
