- From: <bugzilla@jessica.w3.org>
- Date: Mon, 04 Jun 2012 14:20:57 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262 --- Comment #19 from Glenn Maynard <glenn@zewt.org> 2012-06-04 14:20:56 UTC --- (In reply to comment #18) > > > Now, I feel the third one is the complete resolution. > > > > You can't lock external files that can be modified by other non-browser apps > > for the lifetime of the File object. > > I'm sorry. I meant the *SECOND* one is the best way. > If native files can be usable as a File object, we should take a lock at OS > level while getting its Blob reference. No way. If I drag a file into a web page, it's completely unacceptable for the browser to hold a hard write lock on a user's file until the page decides to let go of the reference. (Worse, it'd have to wait for the reference to be GC'd, which might be much longer. Firefox used to have problems with this when uploading files: after uploading a file with a form, the file stayed locked for a while. This gave me daily headaches--I couldn't delete files after uploading them.) Scripts must deal with errors anyway, as there will always be error cases for File. This is just an error. -- 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 Monday, 4 June 2012 14:22:07 UTC