Closed
Bug 161521
Opened 23 years ago
Closed 23 years ago
Non-ascii coding broken after viewing attachment in message body pane
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 110729
People
(Reporter: serhunt, Assigned: nhottanscp)
Details
Attachments
(1 file)
(deleted),
application/octet-stream
|
Details |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1b) Gecko/20020802
This happens in both Mail and News
1. get QuickTime plugin installed and working
2. open Compose window, attach a .mov file, send it to yourself
3. compose a message with 'test us-ascii' in the subject line, switch to Russian
keyboard and type some Russian text. Don't touch Char Coding menu. Send to yourself.
4. compose yet one more message with 'test koi8-r' in the subject line, switch
to Russian keyboard, type text. Go to View/Char Coding menu and change it to
Cyrillic Koi8-R. Send to yourself.
5. get new messages
6. see both test messages displaying Russian correctly (despite one of them has
wrong content-type header, is this a feature?)
7. open the message with the attachment, double click on the attachement, it
will play the movie in the message body
8. go back to 'test us-ascii' message, see it fine
9. go back to 'test koi8-r' message, see garbage
Expected: messages with correctly set content-type header should survive viewing
attachments and still display char coding correctly
Closing and reopening the whole mail-news window cures the situation.
This bug could be related to bug 38109 and/or bug 58950 but does not seem to be
a dup of either of them.
Comment on attachment 94356 [details]
sample movie file
Please save it locally as samle.mov and then attach wnen doing Step 2 in the
original bug report
Attachment #94356 -
Attachment description: Sample movie file, please save it locally as samle.mov and then attach wnen doing Step 2 in the original bug report → sample movie file
Assignee | ||
Comment 3•23 years ago
|
||
This is a dup of bug 110729.
*** This bug has been marked as a duplicate of 110729 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
This is not a dup. This most likely is INVALID as soon as bug 110729 is fixed,
but it is still a true bug for a codepage issue.
bug 110729 is not fixed, and that issue is a general issue with some types of
plugins when they are viewed from mail. There were several bugs filed for .pdf
file (one of them is 110729).
I mean this bug _will_ become invalid when bug 110729 is fixed. But it is not a
dup. Those bugs are about different issues. We may prevent plugins from showing
up in message pane and therefore this bug will go, but is not that wrong that
the code page cannot survive something which happens with one of the messages?
Please note that ALL messages in the mail box are affected after you open this
one specific message. And encouraging moment is that it does not seem to happen
if content-type is us-ascii.
Assignee | ||
Comment 7•23 years ago
|
||
I marked this as a dup of bug 110729 based on the problem described in the
original report of bug 110729.
av, I think you are talking about the solution proposed in bug 110729.
Oh, I see. The original report of bug 110729 does describe the same problem. I
was referring to its summary line which is about something different but
mentions this problem too. OK, so we have two issues. Do we want to keep them in
one bug? They are only related in a sense that fixing one will hide another for
a time being but will not fix it. Although the chances are it will never show up
again, so it's up to you.
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•