175855 - Can not open mail attachments requiring external application (e.g, Word, etc) to view

Status: CLOSED INVALID

(MailNews Core :: Attachments, defect)

Description

[Dmitri Galter]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko

In the 1.2 Beta version on Win2K, if the mail message contains an attachment
requring any external application (like Word, Excel, etc) to view it, it just
"blinks" but fails to do anything (no attempt to open, no suggestion to save, 
etc). Only the attachemnts that can be natively viewed in Mozilla are opened 
(e.g, *.jpg files). It all works fine in 1.2 Alpha. Downgrading back from
Beta to Alpha (which is quite a nightmare in itslef, BTW) does the trick and 
mail is working properly again. 

Reproducible: Always

Steps to Reproduce:
1. Find a mail message with, say, Word attachment.
2. Double-click on the attachment.
3.

Actual Results:  
Nothing. Babkes. Nada :)

Expected Results:  
Either automatically open the attachment using the correct helper application,
or offer the dialogue asking to choose between opening the attachment or saving
it to the disk.

Comment 1

[notfoo]

happens for me too on win xp.

Comment 2

[Rainer Bielefeld]

WFM with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021028

Comment 3

[Max Kanat-Alexander]

Have you tried using a clean profile? Unfortunately, mozilla (especially the
alphas and betas) is only supplied for testing, and this new installs often
require starting with a clean, new profile.

-M

Comment 4

[notfoo]

The clean profile idea seems to be it.  Had to renew profile for another issue, 
bug went away.

Comment 5

[Max Kanat-Alexander]

Cool, then. The profile thing is a known issue, so I'm just going to close the
bug. (It gets marked "INVALID" because there isn't anything nicer to put.)

Thanks for the bug report, though. It was pretty well written. I hope you keep
helping us out with Mozilla!

-M

Comment 6

[Dmitri Galter]

Verified with clean profile for Mozilla 1.2.1, the problem went away.
We can close this bug now.