This is similar to bug 70484 and bug 30841 but actually seems to fall somewhere in between. It is unlike 70484 because there is a noticeable behaviour that happens before the window goes keydead. It is unlike 30841 because this behaviour is erratic and is does not seem to be caused by an avoidable user action. I have noticed it most on pages with many links (e.g. http://plastic.com or in slashdot.org stories with many responses). REPRODUCIBLE: rarely 1. Go to a page with lots of links 2. Find one you think is interesting 3. Right click to Open Link In New Window 4. Wait for a really long time (because the right-click menu is sometimes sloooow) 5. Right click again. menu works. new page opens. 6. Original window is keydead. Note that on Step 4 I really do wait a long time. I am guessing that the popup window creation is somehow silently failing but that the handler creation is not and that the handler is then stealing the keystrokes.

Hmmm, build info does not seem to have gotten into the report. Build ID: 2001072303 I started noticing increased keydead windows a few builds before this but I did not notice the above pattern until this build.

Dupe of bug 70812?

This should be tracked by bug 70812 but it is not a dupe.

This is a duplicate of bug 30841 -- Double right-clicking on a page disables keyboard. I experience key dead only when i double clik on the browser window. The other scenario mentioned in this bug does not cause browser page to go key dead -- wfm. *** This bug has been marked as a duplicate of 30841 ***