169729 - Mozilla fails to add .eml when saving mail

Status: RESOLVED WORKSFORME

(Core Graveyard :: File Handling, defect)

Description

[Henryk Plötz]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.1) Gecko/20020826

When saving a mail using a custom name the extension .eml is not added. It is
added if you leave the default name "nachricht" without editing.

Reproducible: Always

Steps to Reproduce:
1. Highlight a message in the message list.
2. Use Datei -> Speichern unter -> Datei
3. The default name is "nachricht". Do nothing but simply hit "Speichern".
4. Use Datei -> Speichern unter -> Datei
5. Enter a different name, for example "bla" and hit "Speichern".

Actual Results:  
After step 3 a file "nachricht.eml" is created. After step 5 a file "bla" is
created, without any extension.

Expected Results:  
It should do the same in both cases, that is: either always add an extension
when none is given or always not add an extension when none is given (and a file
type is selected). Most windows programs do the first, so Mozilla should always
add the correct extension when none is given.

I'm using the localized build for de-AT. This bug is similar to bug 26310,
however this is not fixed.

Comment 1

[Robert Kaiser]

I don't think we should add extensions that the user doesn't specify (it's clear
we shouldn't do that on *ix, I'm not completely sure about Windows).

Anyway, it's not me to care about that bug, --> File Handling

Comment 2

[R.K.Aa.]

*** Bug 170277 has been marked as a duplicate of this bug. ***

Comment 3

[Mike Cowperthwaite]

Henryk Plötz, this problem seems to have been addressed several times -- bug 
31096, bug 57113 -- and yet I still see it present in 1.3 Final.  However, it 
apparently has been fixed sometime during the 1.4 development -- 1.4b-0516 works 
correctly.  If you're using a 1.4 build, or once 1.4 Final is released, please 
verify this is so.

Comment 4

[Mike Cowperthwaite]

*** Bug 171361 has been marked as a duplicate of this bug. ***

Comment 5

[Mike Cowperthwaite]

Henryk Plötz, can you confirm this is working for you with 1.4 Final?

Comment 6

[Henryk Plötz]

Yes, as far as I can see it is fixed in 1.4 final.

Comment 7

[Mike Cowperthwaite]

Reopening to fix resolution

Comment 8

[Mike Cowperthwaite]

Henryk Plötz, please use "WorksForMe" instead of "Fixed" unless a patch is 
specifically submitted for this bug.