Closed
Bug 72549
Opened 23 years ago
Closed 23 years ago
Non-ascii Subject doesn't show up in the thread
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: marina, Assigned: nhottanscp)
Details
**** observed with 2001-03-19 build **** Steps to reproduce: - compose a mail with non-ascii header; - sebd and get it; //note: therad pane is blank
this is a non-ascii only, the generic bug 72477 got fixed in this build 2001-03-19-04
I can't reproduce it on my machines. (linux, win32 and Mac 2001-03-19-12 build)
i am using the latest build eventhough the build ID says 19-04 (should be 19-12) and i don't see non-ascii headers
let me add some observations: - it happens only on the Inbox on IMAP ( but IMAP Inbox is the largest folder i have~ 6000 messages), i can copy it to other folders and see it just fine. So maybe Inbox's size has to play a role in it. All old non-ascii message in the Inbox are blank now.
i do see non-ascii header with the new build 2001-03-20, wfm???
i am marking it worksforme for now.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
i am reopening this bug because it looks like after certain combination of steps involving account switching this condition maybe be reproduced. I am seeing it again in today's build and it's so sticky that neither restarting nor rebooting nor reinstalling can take it away. I will leave this bug open for now and will addthe exact steps to reproduce it as soon as i see what leads to it. It might be that somebody in Mozilla community see it as well.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 10•23 years ago
|
||
Does this still happen?
Reporter | ||
Comment 11•23 years ago
|
||
i am not able to reproduce it in current builds, markiing as wfm
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WORKSFORME
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
•