Closed
Bug 110860
Opened 23 years ago
Closed 23 years ago
QuickSearch: after returning from results to folder view threading is messed up
Categories
(SeaMonkey :: MailNews: Message Display, defect, P1)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.9
People
(Reporter: laurel, Assigned: naving)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Using nov 19 commerical trunk build
After returning from Quick Search results to a threaded view, particularly if
you were viewing a large/nested thread(s), the threading is majorly messed up.
I know we have problems switching some other views (see bug 102997), but this is
worse and very noticeable in newsgroups.
1. Open a newsgroup, threaded mode. QuickSearch bar is shown.
2. Expand several threads, preferrably fairly large/nested threads.
3. Type text in the QuickSearch bar which will match the subject of one of the
large threads.
4. In the QS results, select a reply of the thread.
5. Clear the QS text by backspace or delete the text. This returns you to the
folder view. Notice how jumbled the threading is.
Result: threading is crapped out when returning from QS results to folder view
which had been in threaded view with some large threads expanded. Will attach
some screenshots.
Assignee | ||
Comment 1•23 years ago
|
||
I have also seen this lately, thanks for filing it. probably better to build
the threaded view from scratch rather than caching it.
Yeah, it gets extremely messed up sometimes. Switching to another sort or
choosing thread again doesn't seem to help (may even exacerbate the scene), must
switch to another group and back (which isn't exactly a speedy remedy!).
Updated•23 years ago
|
Assignee | ||
Comment 6•23 years ago
|
||
fix checked in.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Looks OK using feb01 commericial trunk build: win98, mac OS 10.1, linux rh6.2
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•