Closed Bug 110370 Opened 23 years ago Closed 23 years ago

QuickSearch: Show msg pane after return from QS won't load content

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.0.1

People

(Reporter: laurel, Assigned: naving)

References

(Blocks 1 open bug)

Details

Using nov15 commercial trunk build

When returning to the folder view from QuickSearch results with the message pane
closed, the selected message won't load when the message pane is opened again.

1.  Open a mail folder or newsgroup with Search bar shown, message pane can be
open or closed.
2.  Select a message in the folder/group.
3.  Type some text in the search bar which will provide a few matches.
4.  Select a message in the search results, leave message pane closed.
5.  Return to folder view by clearing the search text field (backspace or delete
text).
6.  You're taken back to the folder view and message (which was selected in step
#2) is selected.
7.  Open the message pane.
 
    Result:  Message pane is blank, contents not loaded.
    Expected:  Selected message should load.

Note: if you select a different message when returning to folder view before
opening message pane, that newly selected message will indeed display contents
when pane is opened.
Keywords: nsbeta1
QA Contact: esther → laurel
Blocks: 106943
still exists dec14 commercial trunk
Status: NEW → ASSIGNED
Keywords: nsbeta1nsbeta1+
Priority: -- → P3
Target Milestone: --- → mozilla0.9.9
Depends on: 119965
moving to 1.0.1
Target Milestone: mozilla0.9.9 → mozilla1.0.1
fixed
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
We have a different selection preservation in current builds, but the bottom
line for this bug is the preserved selection does indeed load if the message
pane is snapped open once you're back in the folder view.

Marking verified with jan 29 commercial trunk build: win98, mac OS 9.2, linux rh6.2
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.