- From: <bugzilla@jessica.w3.org>
- Date: Thu, 18 Apr 2013 00:06:25 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19594 --- Comment #10 from Arun <arun@mozilla.com> --- > I don't think it's needlessly cautious --- I think leaked Blobs could be a > real problem. Auto-revoke by default would have been the right thing to do > if we'd done it that way from the start (which would have required have a > good spec for auto-revoke from the start, which we still don't have!). (In reply to comment #9) I'm honestly not sure it's too late to fix this to be right, especially since we're not sure what's broken, but we are sure that leaked Blob strings can be a "real problem." What can we do to fix the autoRevoke behavior to be better, or address the nits you may have (per Comment 9)? Right now autoRevoke=true is tied in with HTML's global script cleanup steps. Advice appreciated, maybe on the public listserv (public-webapps@w3.org) if you think this bug isn't right. Spec at http://dev.w3.org/2006/webapi/FileAPI/ -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Thursday, 18 April 2013 00:06:26 UTC