Closed
Bug 454352
Opened 16 years ago
Closed 15 years ago
Newsgroup message not displayed immediately after opening an attachment
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: kenny, Unassigned)
Details
(Whiteboard: closeme 2009-02-05)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1 Build Identifier: version 2.0.0.16 (20080708) and 3.0b1 Uncached newsgroup message failed to be displayed in Message Pane immediately after opening a binary attachment. Reproducible: Always Steps to Reproduce: 1. Select a message with attachment (we call this message A) 2. Double-click or select open to load an attachment in message A 3. At the open file dialog, open the attachment file with an application or cancel 4. Return to Thunderbird without changing the nntp server or thread 5. Select any another unread message in the same newsgroup that was not previously loaded Actual Results: 1. message display view is empty 2. attachment pane lists the same files as in message A Expected Results: Contents of the selected message should be displayed. Temporary workaround: 1. Select yet another message (message C or message A), contents will be displayed correctly 2. Re-select message B to view its contents
This problem is only specific to NNTP thread views. IMAP appears to be working fine. The default character encoding of the newsgroup subscription used in the above steps is set to Chinese Traditional (Big5-HKSCS), in case it matters. Application-wide default is UTF-8.
Comment 2•16 years ago
|
||
Can you produce an NNTP log of the session (preferably with a recent trunk nightly)? <https://wiki.mozilla.org/MailNews:Logging>
Whiteboard: closeme 2009-02-05
Comment 3•15 years ago
|
||
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•