Closed Bug 268658 Opened 20 years ago Closed 20 years ago

Modified temporary file - user should be promted to save it when closing it - when attachment is opened in external program (e.g. Word)

Categories

(Thunderbird :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 220808

People

(Reporter: firefox, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Major usability issue:
When attachment is opened from Thunderbird (e.g. .doc file), Thunderbird creates
temporary file for the external program (e.g. Word in this case).
However: when user modifies the file and saves changes, file is lost after
closing the Thunderbird - that means any and *all* changes to the file are lost.

One of my friend (very experienced with PC) have been editing one attachment and
then just saved it and closed Thunderbird. What happened: no changes has been
saved to the attachment and he had to edit it again (*4 hours* of work lost).

Solution: since attachments are being kept encoded in one file (am I correct
here?), any changes done to the attachment should be reporduced in this encoded
file, too.

Another solution: Make temporary file (opened attachment file) READ ONLY, so
when the users tried to save the changes, he is prompted of this and offered to
make a copy of the file isntead (e.g. Microsoft Word follows this when file is
makred as read only).

Reproducible: Always
Steps to Reproduce:
1. Open attachment (e.g. text file)
2. Modify the file (write random characters)
3. Save the file
4. Close the file

Actual Results:  
No changes are saved.

Expected Results:  
All changes are saved.

See the solutions proposed above in the details.
Resolving as dupe like Bug 244934.

*** This bug has been marked as a duplicate of 220808 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.