On Thu, Jan 12, 2012 at 3:45 PM, Glenn Maynard <gl...@zewt.org> wrote:
> FYI, I don't think this is clear for File from the spec. It's even more > important if File objects are stored in History or IndexedDB; that it > should be a *shallow* copy, with enough information stored to invalidate it > if the underlying file changes, doesn't seem to be specified. (As far as I > know, nobody implements that yet; being able to eg. retain open files in > History states would be extremely useful. > Gecko nightlies are capable of storing File objects in IndexedDB, We are doing "deep" copies (what is retrieved from the database is always a copy of the file as it was when it was placed in the database). - Kyle
