Closed
Bug 129988
Opened 24 years ago
Closed 24 years ago
No advance to next message if message pane focused
Categories
(SeaMonkey :: MailNews: Message Display, defect, P1)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: v.kazmirenko, Assigned: sspitzer)
References
Details
(Keywords: access, regression)
Attachments
(1 file, 1 obsolete file)
|
901 bytes,
patch
|
ssu0262
:
review+
Bienvenu
:
superreview+
brendan
:
approval+
|
Details | Diff | Splinter Review |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9+)
Gecko/20020309
BuildID: 2002030908
In Messenger while rading news (I use offline) if focus placed on message body
(right-bottom pane in 3-pane view) space bar and 'n' do not advance to next
message. However, 'Next' button on toolbar works. When subjects pane is focused
(right-top) then both shortcuts work.
Reproducible: Always
Steps to Reproduce:
1.Go to newsgroup that contains unread messages
2.Select message body pane
3.Press 'n' or space bar
Actual Results: Message scrolls to the end but there no advance to next unread.
Expected Results: Next unread message should be displayed when current is
screolled to the end.
| Assignee | ||
Comment 1•24 years ago
|
||
thanks for the bug, victor.
I'm pretty sure I caused this regression with my checkin for #128101
I'll tackle this first thing monday morning.
Severity: normal → critical
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Keywords: nsbeta1,
regression
Priority: -- → P1
Target Milestone: --- → mozilla1.0
Updated•24 years ago
|
| Assignee | ||
Comment 2•24 years ago
|
||
| Assignee | ||
Comment 3•24 years ago
|
||
I've tested and made sure that his fix doesn't break the fix for #128101
I'll go seek reviews.
Comment 4•24 years ago
|
||
Comment on attachment 73537 [details] [diff] [review]
fix, boy do I suck ass for this.
R=ducarroz
Attachment #73537 -
Flags: review+
Comment 5•24 years ago
|
||
Comment on attachment 73537 [details] [diff] [review]
fix, boy do I suck ass for this.
sr=bienvenu
Attachment #73537 -
Flags: superreview+
| Assignee | ||
Comment 6•24 years ago
|
||
Attachment #73537 -
Attachment is obsolete: true
Comment on attachment 73539 [details] [diff] [review]
simpler patch, as suggested by ssu. I still suck ass.
r=ssu
Attachment #73539 -
Flags: review+
Comment 8•24 years ago
|
||
Comment on attachment 73539 [details] [diff] [review]
simpler patch, as suggested by ssu. I still suck ass.
sr=bienvenu
Attachment #73539 -
Flags: superreview+
Comment 9•24 years ago
|
||
Comment on attachment 73539 [details] [diff] [review]
simpler patch, as suggested by ssu. I still suck ass.
a=brendan@mozilla.org for the 1.0 trunk.
Who is still using tabs? *shudder*
/be
Attachment #73539 -
Flags: approval+
| Assignee | ||
Comment 10•24 years ago
|
||
the tabs are fixed locally, that patch is -uw.
fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 11•24 years ago
|
||
Could anybody kindly explain me what is the meaning of 'Resolution: fixed'? Am I
right that fix is included in following nightly? If so 2002031103 has the same
problem...
| Assignee | ||
Comment 12•24 years ago
|
||
resolved fixed means I checked in the fix.
you'll have to wait for the next build that includes this fix.
in this case, that's tomorrow's build.
Comment 13•24 years ago
|
||
*** Bug 130142 has been marked as a duplicate of this bug. ***
Updated•24 years ago
|
Comment 14•24 years ago
|
||
OK using mar14 commercial trunk: win98, mac OS 10.1, linuxrh6.2
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•