25240 2014-04-02 21:10:24 +0000 Blob.close() shouldn't throw when invoked more than once. 2014-05-07 15:06:59 +0000 1 1 1 Unclassified WebAppsWG File API unspecified PC All RESOLVED FIXED P2 normal --- 1 arun arun glenn public-webapps zcorpan public-webapps-bugzilla oldest_to_newest 103297 0 arun 2014-04-02 21:10:24 +0000 See Bug 24576 Comment 11. Blob.close() should, if invoked more than once, be a no-op. 103303 1 glenn 2014-04-02 23:58:33 +0000 For example, var xhr = new XMLHttpRequest(); xhr.open("GET", "/foo"); xhr.onloadend = function() { blob.close(); console.log("XHR finished"); } xhr.onload = function() { finishWorking(); } xhr.onerror = function() { blob.close(); } xhr.send(blob); would result in onloadend throwing and not doing anything after blob.close() on the onerror path, since onerror already closed the blob, even though it's in exactly the state the developer wanted--the blob is closed. (The above isn't the best way to do this, of course--you should just call blob.close() immediately after xhr.send--it's just an example of something harmless being turned into a bug.) 105274 2 arun 2014-05-07 03:06:57 +0000 Blob.close() no longer throws when invoked more than once: http://dev.w3.org/2006/webapi/FileAPI/#close-method 105285 3 zcorpan 2014-05-07 07:23:12 +0000 Can you remove "do nothing, since context object is already closed, and "? 105307 4 arun 2014-05-07 15:06:46 +0000 Done: http://dev.w3.org/2006/webapi/FileAPI/#dfn-close