-----Original Message----- From: Jonas Sicking [mailto:[email protected]] Sent: Wednesday, May 29, 2013 3:25 PM To: SULLIVAN, BRYAN L Cc: Charles Pritchard; [email protected]; [email protected] Subject: Re: Filesystem events
On Wed, May 29, 2013 at 3:17 PM, SULLIVAN, BRYAN L <[email protected]> wrote: > From: Charles Pritchard [mailto:[email protected]] > Sent: Wednesday, May 29, 2013 3:08 PM > To: [email protected] > Cc: [email protected] > Subject: Re: Filesystem events > > > > We didn't come to much of a resolution. > It was suggested that the current behavior in browsers was incorrect; that > the File should become inaccessible if/when it changes. > > <bryan> I disagree, the fact that re-accessing a file object loads the > latest version of the file is a valuable feature IMO, even if it was not > intentional. I don't know if preventing that is what you meant, but further > to require that the user reselect a file if it has changed would be a UX > killer. File objects should be immutable. That was one of the core design principles that they were built around. If we want <input type=file> to provide "live" access to on-disk files, then new File objects should be returned from HTMLInputElement.files whenever the on-disk files change. That would need to be defined by the HTML spec though. <bryan> OK, but that sounds like one of those "good UA design" principles that ignores the actual effect upon apps and users. I would prefer to keep this "bug" around until the new/better design is implemented.
