293775 - KeyPress event still active while dialog box open - causes uncaught exception

Status: VERIFIED WORKSFORME

(Firefox :: General, defect)

Description

[Walt Stoneburner]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

The Javascript console reports this error within Firefox:
Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMTreeWalker.nextNode]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://global/content/bindings/button.xml :: fireAccessKeyButton :: line 93" 
data: no]

...when the browser is processing a keyboard event, has a dialog box open, and
another keyboard event arrives.

Reproducible: Always

Steps to Reproduce:
1. Catch a keydown event and have it open an alert box.
2. While the alert box is still open, press another key (not space or enter,
which closes the alert box).

Actual Results:  
The browser threw an NS_ERROR_UNEXPECTED exception that was uncaught.

Expected Results:  
The software should not have been honoring the keyboard presses until the dialog
box was closed.

Comment 1

[Stephen Martin]

This is not Mac specific.  I have the same issue on WinXP.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0

Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMTreeWalker.nextNode]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
chrome://global/content/bindings/button.xml :: fireAccessKeyButton :: line 93" 
data: no]

onChange or onClick of different fields fire same Javascript function that uses
window.alert.  Pressing any key other than Space or Enter while alert is
displayed causes error in JS Console. 

Comment 2

[William Bumgarner [:zsinj]]

When testing a bug's validity, it's best to use a recent build, not 1.0.

Is this still reproducable with a nightly build? http://www.mozilla.org/developer

Comment 3

[Walt Stoneburner]

I believe I did check the nightly build at the time of submission.  However, GOOD NEWS, I just tried the 
URL with the page that simulates the problem.  It appears to be fixed in the nightly build.  HURRAY!

Can anyone else confirm?

Comment 4

[Kevin Brosnan]

WFM as there is no patch