145315 - Keyboard access loss on second load

Status: RESOLVED WORKSFORME

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Cameron Hall]

Initial Install goes fine, full install.  Win98SE
First use, fine.  Can ALT-b to bookmarks, use up down arrows to scroll pages etc.
Exit browser
Reload.
No keyboard entry of ALT-b can be done at all.  Just chimes at me (windows sound
output via soundcard)
In fact, just testing while writing this message, no ALT- commands workable. Due
to my being visually impaired, the keyboard is a major navigational tool.
This bug has been in the last several versions, and thought it being so glaring,
it would be cought. :)

Comment 1

[Dennis Daniels]

WFM
Mozilla 1.2b
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2b) Gecko/20021016
tested alt+b
closed browser
tested alt +b again
no problem here

Comment 2

[tyl2]

WFM 2003022814 on WinXP. Bug should be closed given one old report only.

Comment 3

[Frank Wein [:mcsmurf]]

Reporter: Does this bug still happen with a current Mozilla build?

Comment 4

[phil]

It happens to me all the time using the 1.3 release under Linux.

Comment 5

[phil]

Some additional info, using 1.3 under Linux:

First use, fine.  Browser eventually locked up trying to get a page, so I closed
it and restarted.

At that point, all keypresses were ignored.  Likewise on the third and fourth
tries.

In desperation, I went into my profile and deleted history.*.  Firing it up again
gave me working keypresses again.

Comment 6

[Dave (DK) Harding]

Cameron, are you still experiencing this bug?

Phil: Has the problem reoccured since deletetion?  What keyboard are you using?
 Also, have you tested keystrokes in different parts of the Mozilla UI (User
Interface), i.e. in a form, in the address bar, in edit-->Prefs?  I had a
similar problem in Galeon where I couldn't type in forms but could type in the
address bar.

Comment 7

[phil]

Dave:  Thanks for responding.

It hasn't reoccured yet, but I haven't had a similar lockup yet, where I needed
to bail and restart the browser.

My keyboard is a bog-standard microsft natural.  (104? keys, split in the middle
for people trying to avoid fscked-up wrists.)  No keyboard remapping programs or
the like running.

Comment 8

[phil]

Some more info, after I've noticed more patterns:

- It happens during the first load as well, after just starting up, quite often.
- The keyboard is completely ignored in all main windows.  Keyboard shortcuts,
  urlbar, sidebar (e.g., search panels, you name it.
- Popping up the File -> Open Web Location... box and entering a URL there works.
  This also restores the keyboard input.

Comment 9

[phil]

One last additional note.  (This happens almost every time I start the browser,
on multiple machines, so I'm getting lots of practice.)

Re comment 8, which is the only reliable way I've found of restoring the
keyboard:  it's not the popping up that does it, because most of the time I
can't type anything in that input field either.  I just click enter and go to
whatever was in there before.  (Can't even hit the Enter key.)

What restores input, apparently, is when the New Web Location window goes
away, and focus returns to the main browser window.  At that point, all keyboard
entry works fine again.

Comment 10

[Glenn Douglas]

Can't reproduce on winxp, Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.5b) Gecko/20030716.

Comment 11

[Vincent de Phily]

I found a web page that triggers the bug reproductively on my machine (Mozilla/5.0 
(X11; U; Linux i686; fr-FR; rv:1.5) Gecko/20031126) : it's the login form of gallery. 
 
http://gallery.menalto.com/
modules.php?set_albumName=samples&op=modload&name=gallery&file=index&include=view_album.php 
 
Load mozilla, go there, select any sample gallery and click the "login" link. A windows 
pops up, but keyborad seems now deactivated (keyborad was fine on previous page). 
This makes the login page kind of useless :p 
 
 
I edited my own gallery's login.php file to REMOVE the following lines : 
>>>>>>>>>>> 
<script language="javascript1.2" type="text/JavaScript">                                      
<!--                                                                                          
// position cursor in top form field                                                          
document.login_form.uname.focus();                                                            
//-->                                                                                         
</script>  
<<<<<<<<<<< 
And now the login page on my website doesn't disable the keyboard. 
 
 
It seems unlikely that this javascript could be the only culprit though : a lot of 
webpages use it (google's main page to name only one) whitout triggering the bug. 

Comment 12

[Asa Dotzler [:asa]]

Unable to reproduce on the latest windows builds. Please reopen if you can
reproduce with a clean install of 1.7 beta or newer and a new profile.