Closed Bug 315802 Opened 19 years ago Closed 14 years ago

keycode of mousedown event should be "0" instead of undefined

Categories

(Firefox :: General, defect)

2.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: hongg, Unassigned)

Details

(Whiteboard: [CLOSEME 5-15-2010])

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051109 Firefox/1.6a1

I register a mousedown event of an anchor, and after I click the anchor, the keyCode I get is "undefined", which was "0" in older version of firefox and other browsers.

ex:
eventHandler(e){
	if (isIE){
	   return;
	} else {
	   alert(e.keyCode)
	   return;		
	}
 }

Reproducible: Always

Steps to Reproduce:
1.register the mousedown
2.fire the mouse down event
3.alert value is "undefined" which should be "0"

Actual Results:  
get an unwanted keyCode value "undefined"


some script function use keyCode==0 to test if it is a mouse event
so if the return value is "undefined", 
the functions won't work well
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.