Re: [w3c/FileAPI] Remove definition of Blob.close() and all related terms. (#68)

Yes, chrome implemented some attempt of a close() method (never shipped it though), but it had many bugs (largely because the functionality was never really specified), and actually specifying what close would do would be really complicated. It also was never the case that closing a blob in chrome would immediately cause anything to be freed, as there could be other references to the same data, etc, so even back when chrome had a hard limit on how large the total number of blobs could be just closing one wouldn't be enough to know that you could create more, as closing/freeing memory/disk space is inherently an async operation.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/pull/68#issuecomment-367050922