bugzilla.mozilla.org will be intermittently unavailable on Saturday, March 24th, from 16:00 until 20:00 UTC.

clicking on an attachment a second time will fail to open it



MailNews Core
15 years ago
10 years ago


(Reporter: Orest Skrypuch, Assigned: (not reading, please use seth@sspitzer.org instead))


Firefox Tracking Flags

(Not tracked)




15 years ago
User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4b) Gecko/20030509
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4b) Gecko/20030509

This is with for example a .doc file (any file will work), you have mime type
application/msword set to run WordPro on the file (the system default), clicking
on the file works the first time, but any and all subsequent times WordPro opens
with an empty file.

If you go to the "temp" directory and erase the file, as well as the dup renamed
file that occurs after the second attempted opening of the file, it works again
-- once.

The subsequent copies of the file in the temp directory get renamed as
original-1.doc, original-2.doc, etc.

Reproducible: Always

Steps to Reproduce:
1. Receive a .doc attachment
2 [review]. Click on it to load it - works OK, close WordPro
3. Click on it a second time 

Actual Results:  
WordPro opens with a blank file

Expected Results:  
WordPro opens with the attached file


15 years ago
OS: other → OS/2

Comment 1

15 years ago
I've done some more testing.

Apparently Lotus Word Pro will not load a file with a filename that has a hyphen
in it, at least not if it is "dropped" on the application.

You can File|Open such a file.

Is there a workaround, perhaps say the ability in Mozilla to instead insert a
":" or "_" instead of a hyphen in the second copied file?

* Orest

Comment 2

15 years ago
Sorry, this is a WordPro bug and we aren't going to workaround it.

My suggestion is to use a CMD file that renames the file.
Last Resolved: 15 years ago
Resolution: --- → INVALID
Verified invalid per mkaply's comments.
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.