Comment #2 on issue 28251 by [email protected]: Chrome fails to follow files once moved on the filesystem http://code.google.com/p/chromium/issues/detail?id=28251
Firefox also FAILs here, but this is something Chrome should definitely do if it's going to feel like a native Mac application. Users expect files to behave like objects, not paths. Good Mac applications keep track of your files and they do The Right Thing, even when files move. If a file is moved while you're editing it, a well-designed Mac application will inform you, and offer to save your changes to the new location, or let you choose another one. In this case, doing The Right Thing means behaving like Safari. This is especially true since, by default, Chrome keeps a list of all downloaded files. Over time, files on that list are practically guaranteed to have been moved, and thus the list gradually becomes less useful. If it kept track of moved files, on the other hand, the list could be more useful over time, bringing to light files that had long since worked their way into the deeper recesses of the filesystem. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
