- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 Apr 2014 21:15:55 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24576 Arun <arun@mozilla.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #27 from Arun <arun@mozilla.com> --- (In reply to Simon Pieters from comment #21) > So you have changed your mind about createObjectURL? Yes; I'm sorry I've muddled comments, and inflated this bug about other things. THIS bug is fixed: http://dev.w3.org/2006/webapi/FileAPI/#creating-revoking > (In reply to Arun from comment #19) > > So, after chatting with Jonas on IRC, I think Comment 11 is right about not > > throwing for URL.createObjectURL and URL.createFor, > > Comment 11 is about close(). You're right. This should be a new bug, just to keep things clear: Bug 25240 > So the benefit you see with close() throwing is that it's consistent with > readAs*? I think that's not so convincing. I think similar reasoning for > createObjectURL() applies to close() -- throwing puts the burden of > try/catch on a developer just trying to close a Blob. (Reopening for > reconsideration/clarification about close().) readAs* shouldn't throw on neutered Blobs. This is Bug 25241. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Wednesday, 2 April 2014 21:15:57 UTC