Closed
Bug 185578
Opened 23 years ago
Closed 18 years ago
The message window doesn't have keyboard focus by default
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: arnova, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021211
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021211
When opening mail from for example your inbox and the message is viewed in a
seperate window, the window doesn't get keyboard focus (initially). One first
has to mouseclick on the message to make for example the cursors (up/down) work.
Reproducible: Always
Steps to Reproduce:
1. Open a message from your inbox
2. Try to use the cursors to navigate through the email
3. Observe that you first have to click on the message to make it work.
Actual Results:
The cursors don't move the page.
Expected Results:
The cursors should move the page (without first having to mouseclick on the message)
Comment 1•23 years ago
|
||
Same with
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.2.1) Gecko/20021130
This happens not only when message is displayed in seperate window
but also in message window of 3pane layout.
Comment 2•23 years ago
|
||
User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.2.1) Gecko/20021130
O.k. in 3pane layout keyboard focus only moves from headers to message window
when explicitely requested with a click. No reason to worry about that, sorry.
Still request to correct seperate window behaviour.
*** Bug 188240 has been marked as a duplicate of this bug. ***
Comment 4•22 years ago
|
||
WFM with WinXP rv:1.5b Gecko/20030731
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•21 years ago
|
Assignee: sspitzer → mail
Comment 5•18 years ago
|
||
up+down WFM without click
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070222 SeaMonkey/1.1.1 XpcomViewer/0.8.9
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•