Closed
Bug 460448
Opened 16 years ago
Closed 15 years ago
Newsreader: the new message header pane doesn't display references
Categories
(Thunderbird :: Message Reader UI, defect)
Thunderbird
Message Reader UI
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bugzilla.i.sekler, Unassigned)
References
Details
(Keywords: regression)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081016 Firefox/3.1b2pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2pre) Gecko/20081016 Thunderbird/3.0b1pre
Before the refactoring of the message header pane, the normal view of message headers contained also a list of clickable references, which allowed a quick navigation backwards in a newsgroup thread. This list was displayed regardless of the value of the preference mailnews.headers.showReferences (that was wrong). Now, with the new message header pane, the references are not displayed at all, even if mailnews.headers.showReferences is set to "true" (this is what this bug is about).
This applies also to View => Headers => All.
Reproducible: Always
Steps to Reproduce:
1. Set the preference mailnews.headers.showReferences to "true".
2. Select a newsgroup message which is a reply to another message in a thread.
Actual Results:
No references.
Expected Results:
The references are listed.
A screenshot comparing the old and the new message header pane: https://bugzilla.mozilla.org/attachment.cgi?id=340328
Reporter | ||
Updated•16 years ago
|
Keywords: regression
Version: unspecified → Trunk
Comment 1•16 years ago
|
||
Confirmed.
Comment 2•16 years ago
|
||
If someone wanted to come up with a patch for this, that would be great; marking wanted+ for Tb3.
Component: Mail Window Front End → Message Reader UI
Flags: wanted-thunderbird3+
QA Contact: front-end → message-reader
Comment 3•15 years ago
|
||
This was fixed at some stage, I think I even reviewed the patch for it. Marking as WFM
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Comment 4•15 years ago
|
||
right, that was bug 482048 i believe
You need to log in
before you can comment on or make changes to this bug.
Description
•