Closed
Bug 19504
Opened 25 years ago
Closed 24 years ago
going to next unread displays next unread, but doesn't show in header display pane.
Categories
(SeaMonkey :: MailNews: Message Display, defect, P3)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
M16
People
(Reporter: leaf, Assigned: alecf)
References
Details
this is probably a nuisance thing, but it would help to see what thread the unread message was in.
Reporter | ||
Comment 1•25 years ago
|
||
cc'ing mscott
Updated•25 years ago
|
Assignee: phil → putterman
Comment 2•25 years ago
|
||
I'm sure this is mine, but I'm not exactly sure what you mean in the summary.
Perhaps, it means that the thread pane doesn't select the next unread message or that the next unread message doesn't scroll to view.
Comment 4•25 years ago
|
||
If that's the case, I thought Alec fixed this last week. Perhaps not.
Comment 5•25 years ago
|
||
maybe he fixed something else because this isn't currently working.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M13
Comment 6•25 years ago
|
||
Alec, is this a dup of your bug on scrolling the tree to make sure the selected item is in view?
Assignee | ||
Comment 7•25 years ago
|
||
close, I need to finish #12895, then there is some minor mail work that must be done.
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 8•25 years ago
|
||
alec checked in his fixes and I used them so that this now works.
Linux Redhat 6.0 (2000-01-11-09 M13) Win_nt 4.0 (2000-01-11-09 M13) When I click on the Next button or select Go|Next|Unread Message, it scrolls to view only 1/3 of the message header. I expect to be able to view the entire header of the message in the thread pane. Reopen this bug for this reason.
Updated•25 years ago
|
Assignee: putterman → alecf
Status: REOPENED → NEW
Comment 10•25 years ago
|
||
reassigning to alecf. This may or may not be your bug. But if we could scroll to the middle or some place that's not the exact bottom, that would be cool.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 11•25 years ago
|
||
this is indeed my bug...however, I don't expect to get to it any time soon :(
Assignee | ||
Comment 12•25 years ago
|
||
so I figured out what's going on here, and unfortunately, it's not pretty. But I have an idea. The tree is in fact behaving correctly by scrolling to the right place, but the headers move AFTER the message has been selected. I'm thinking: 1) we fix the headers problem. I think mscott has looked into this with hyatt 2) when any message is done loading, THATs when we scroll it into view, not before.
Assignee | ||
Updated•25 years ago
|
Target Milestone: M13 → M14
Assignee | ||
Comment 13•25 years ago
|
||
moving M13 bugs to M14 to get them off the radar. (Not to worry, I'm still working on these before my other m13 bugs!)
Comment 14•25 years ago
|
||
Alec says it works ok except the first time you open a folder. In that case, the initial header display comes up after we try to scroll to the right message, obscuring it. This remaining symptom is not a beta stopper.
Target Milestone: M14 → M16
Comment 15•25 years ago
|
||
*** Bug 26027 has been marked as a duplicate of this bug. ***
Comment 16•24 years ago
|
||
*** Bug 32333 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 17•24 years ago
|
||
this just works.. putterman must have fixed it long ago
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 18•24 years ago
|
||
I don't think I fixed this ! Basically, sometimes the next selected message is below the splitter and sometime it isn't. Generally when it's below, it's just below as if there's an off by one error some place. This may be a different bug as well.
Comment 19•24 years ago
|
||
Linux (2000-04-13-11-M15) Win32 (2000-04-13-06-M15) Mac (2000-04-13-05-M15) I see that when I select Go|Next Unread Message, it display the next unread message and the thread pane shows the thread of the Unread message.
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
•