Closed Bug 159114 Opened 23 years ago Closed 15 years ago

Up/Down/PageUp/PageDown initially don't work when reading an email

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: arnova, Unassigned)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1b) Gecko/20020721 BuildID: 2002072104 When one views an email in a seperate (full-screen) window, pgup pgdn and the up/down cursors initially don't work. You first have to click on the background to make them work. Reproducible: Always Steps to Reproduce: 1.Open an email from your inbox in a seperate window 2.try to use the up/down/pgup/pgdn keys 3.And watch that they don't work Actual Results: Nothing happens. Expected Results: The message should be scrolled. Seems like a focus problem to me.
Assignee: syd → sspitzer
Component: Editor: Composer → Mail Window Front End
Product: Browser → MailNews
QA Contact: sujay → olgam
Summary: Cursors initially don't work when reading an email → Up/Down/PageUp/PageDown initially don't work when reading an email
This sounds like a mail problem (or perhaps focus/selection?) -->Mail
Same with me.. I cannot pageup/down, i'm forced to click inside the pane first.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: olgam → message-display
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.