Closed Bug 263300 Opened 20 years ago Closed 20 years ago

# Character in folder name causes incorrect attachment file name

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 243504

People

(Reporter: michael.truss, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Thunderbird cannot handle an attachment filename correctly if their is a # character in the path to the file you are trying to attach. For example, I have a folder named "SA#24 Seoul" somewhere on my D: drive, If I write an e-mail using Thunderbird and try to attach any file from the folder "SA#24 Seoul", Thunderbird will allways give the attachment the filename "SA" with no extension. When the mail is sent, any and all attachments included from that folder will simply have the filename SA Note when placing the cursor over the attachment in the Thunderbird composition attachment pane the full path/filename pops up but with "SA%2324 Seoul" as the folder name for "SA#24 Seoul". This problem does not exist in Netscape 7.1 Email Reproducible: Always Steps to Reproduce: 1. Create a folder with a # in the name e.g. "Test # 25" 2. Copy a few files with different names into the folder 3. Compose an email with thunderbird 4. Try to attach any of the files from the folder to the e-mail 5. For the folder example at 1. all files attached will have the same incorrect filename, i.e. "Test" (the part of the folder name before the # character) Actual Results: All Attached Files have incorrect and identical filename Expected Results: Used the coirrect filenames Note when placing the cursor over the attachment in the Thunderbird composition attachment pane the full path/filename pops up but with "SA%2324 Seoul" as the folder name for "SA#24 Seoul". This problem does not exist in Netscape 7.1 Email
*** This bug has been marked as a duplicate of 243504 ***
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.