Closed Bug 56184 Opened 24 years ago Closed 24 years ago

keyboard navigation not working due to loss in focus

Categories

(Core :: XUL, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 54936
mozilla0.9

People

(Reporter: vparthas, Assigned: saari)

Details

(Whiteboard: [rtm-])

There seem to be some focus problems 1. Can't navigate after logging into mail: Windows only problem (OK on Linux and Mac) - When opening an account enter the password in the login dialog, ok. - Try "N" to go to the next message or the up/down arrow key and nothing happens - I must select an area on the window with the mouse then the navigation keys work. - Also noticed if Password Manager is used then the navigation keys work. There is something about the login dialog that seems to cause the problem. 2. Shift+Tab: Loses focus a. With a message in the thread pane selected, Shift+Tab. No focus in the folder pane, can't use up and down arrow keys. b. With a folder selected in the folder pane, Shift+Tab. No focus in the message pane, can't use up and down arrow keys. c. Yet it Does work if the message pane is selected. Shift+Tab moves focus to the thread pane and the up and down arrow keys Do work. 3. Dont save the password and open mail. a-Enter the password and then try to use Ctrl-1 to launch Navigator- nothing happens. b-open the Edit->Mail/News Account Settings -Focus is not there on any widget and we have to use the mouse.
Blocks: 28520
Keywords: mailtrack, rtm
one defect per bug report, maximum. Please put others in separate reports. Which problem is this report about?
I think the bug report is about how after exiting dialogs focus isn't returned to the main window. In mailnews that means that you can no longer use keyboard navigation to move around the panes. In the browser this means that you can no longer use arrow keys or the space bar to move around in the content window. And in both windows you can no longer use accelerators to open up another window. My guess is that we've probably passed the point where this can get fixed.
I've known about this problem for a while now (3 weeks +), and it got nsbeta3 minused and RTM minused. Sorry, this bug drives me nuts too. It is windows only, and it happens when you dismiss a dialog. Some code danm added to work around a Windows OS bug messes up the focus sequence ever so slightly such that the OS is convinced that the thing focus memory is trying to restore already has focus so I doesn't send the proper messages to the window.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
rtm-
Whiteboard: [rtm-]
A dup of another Mozilla 0.9 targeted bug
Target Milestone: Future → mozilla0.9
Identified the other bug following saari's comment. Marking duplicate of 54936. *** This bug has been marked as a duplicate of 54936 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified duplicate
No longer blocks: 28520
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.