- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jul 2012 16:05:07 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16952 --- Comment #16 from Arun <arun@mozilla.com> 2012-07-12 16:05:05 UTC --- (In reply to comment #14) > Hmm.. I wonder if it would make using Blobs easier if we didn't throw when > trying to read from a neutered Blob. That way the page can be sure that reading > will never throw, and can simply watch for error events. > > I agree that reading from a neutered Blob is generally a bug, and throwing in > cases of bugs is generally a good thing. But I wonder if this might be a case > where not throwing and instead firing an error event asynchronously would > simplify the model for developers. I don't think so. Note that neutering a Blob and then explicitly reading on that Blob is such a bad pattern that throwing seems better than yet another error event. It is probably the result of a mistake, or else something that the developer should catch (e.g. a Blob that's neutered owing to a set of conditions, etc.). -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 12 July 2012 16:05:14 UTC