Closed Bug 290027 Opened 20 years ago Closed 20 years ago

mozilla hangs when an attachment is dragged from the message window to the desktop

Categories

(SeaMonkey :: MailNews: Message Display, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: heinz.hugli, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050319

Normally, the attachment of a message can be copied out of the mailbox by
dragging the attachment icon found in the Mozilla message window to the desktop
or another folder.
When the name of the attachment has accents (like é, â, ...) Mozilla hangs.

The bug is present in previous versions of Mozilla, since the introduction of
the dragging feature.

Reproducible: Always

Steps to Reproduce:
1.Consider a message with an attachement which name has accents (like ü, è, é....)
2.Open the message, drag the attachement to the desktop 
3. Mozilla hangs

Actual Results:  
Mozilla hangs

Expected Results:  
Copy the attachement and resume
With Mozilla 1.7.6, Windows 2000, I see the file getting copied, with no hang, 
but the filename is being truncated starting at the first non-ASCII character.

However, a not-so-new trunk build (1.8b2-0309) copies the file and gives it the 
correct name.  Heinz Hugli, please test your symptom with 1.8b1:
  http://www.mozilla.org/releases/
or a current nightly build:
  http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest/

If the problem is not present in that build, please mark this bug:
  Resolved | WorksForMe
Assignee: sspitzer → mail
Version: unspecified → 1.7 Branch
No response from reporter  => WFM
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
(In reply to comment #2)
> No response from reporter  => WFM

I checked with 1.8b1 which solves the problem.
Problem resolved, 1.8b1 works for me.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.