Comment 5 for bug 73244

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; it; rv:1.8.1.14) Gecko/20080404 Iceweasel/2.0.0.14 (Debian-2.0.0.14-2)
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; it; rv:1.8.1.14) Gecko/20080404 Iceweasel/2.0.0.14 (Debian-2.0.0.14-2)

(See steps.)

Reproducible: Always

Steps to Reproduce:
Suppose to open a remote link in a webpage using an application selected in the "open with/save" dialog. Then Firefox downloads the remote file to a temporary location (and IMHO it should be a bit more smart, but this is bug #415441 already), and launches the application with the downloaded file. Good so far.
Then, if we close Firefox but not the application, Firefox removes the downloaded temporary file.
Actual Results:
The application launched for the (temporary) file can have troubles if it wants to still make use of the file.

Expected Results:
Firefox should not implicitely remove the temporary file, but for example:
- leave it around, either permanently or tracking the application launched with fork() [UNIX, of course]
- manage explicitely it in the downloads, just like Opera does

This was reported as problem in KDE's bugzilla for the KDE 4 application Okular:
  http://bugs.kde.org/show_bug.cgi?id=163363

If the users (after doing the steps before, eg fire Okular from Firefox and close Firefox) selects "Save copy as", they are not able to save it, because the only reference to the file (the temporary file, not even the remote URL that basically all the KDE applications can manage) is gone.

Can also be reproduced with Firefox 3beta5:
  Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5) Gecko/2008050509 Firefox/3.0b5