Re: [FileAPI] Persistent blob urls (#27)

It could even be an entirely new api. E.g. a very light weight `FilePointer` object that can be used from `FileReader` and which does similar book keeping as Blob URLs with regards to outside modifications so that the app has no access to new information. You could then persist it in IndexedDB which wouldn't have to care about the actual file semantics, because only the pointer is part of the transaction not the File itself.

There are so many cases where this would give much better UX than is currently possible for no additional security issues that aren't already there. Then there is the media library case I already mentioned.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/27#issuecomment-178654982