344152 - JavaScript "keyup" event not working on FF 1.5 (Mac)

Status: RESOLVED WORKSFORME

(Core :: DOM: Events, defect)

Description

[Todd Kingham]

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

I just upgraded (July 10, 2006) Firefox from v1.0.7 to v1.5.0.4. After doing so, the JavaScript "keyup" event fails to fire off.

I have been able to duplicate this on two separate systems.

System 1:
MacOS X 10.4 - Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.3) Gecko/20060426 Firefox/1.5.0.3

System 2:
MacOS X 10.3.9 - Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

Both of the systems listed above fail on the keyup event. I have tried using both DOM 0 and Event Listeners and both methods fail to produce any result of the event. In testing I have added keyup event listeners to both INPUT fields and to the document itself with the same result.

I should also note, that the keyup event worked flawlessly on "System 2" listed above prior to the upgrade. 

Also, the keyup event works fine on my PC which is also running Firefox 1.5 under Windows XP service pack 2.






Reproducible: Always

Steps to Reproduce:
1. Go to a webpage with a keyup event tied to a document or document ELEMENT
2. Fire off the event by placing focus on the element in question and pressing any key on your keyboard then releasing it.

Actual Results:  
No results occur. There is no JavaScript exception thrown, just no event occurs. It appears as if the event does not exist or is not recognized.

Expected Results:  
The expected results will vary based on the action written into the JavaScript code. In any case there should be a call to a referenced JavaScript function (which is not happening). 

I chatted with someone in the #firefox IRC channel who said they tested it on FF 1.5 and FF 2 (for Mac) and was not able to reproduce the error. 

But after testing it on my machine and a co-workers machine (with both producing the same results) I feel the issue may not be specific to me.

Comment 1

[Phil Ringnalda (:philor)]

*** Bug 347324 has been marked as a duplicate of this bug. ***

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This WFM on 1.8.1 branch builds (fx2003 and cm11b+).  It wasn't bug 26269 that fixed this (since that's only modifiers), but I know mento fixed other bugs like it for 1.8.1.