views:

2773

answers:

4

A very niche problem:

I sometimes (30% of the time) get an 'undefined handler' javascript error on line 3877 of the prototype.js library (version 1.6.0.2 from google: http://ajax.googleapis.com/ajax/libs/prototype/1.6.0.2/prototype.js).

Now on this page I have a Google Map and I use the Prototype Window library.

The problem occurs in IE7 and FF3.

This is the info FireBug gives:
handler is undefined
? in prototype.js@3871()prototype.js (line 3877)
handler.call(element, event);

I switched to a local version of prototypejs and added some debugging in the offending method (createWraper) but the debugging never appears before the error...

I googled around and found 1 other mention of the error on the same line, but no answer so I'm posting it here where maybe, some day someone will have an answer :).

+3  A: 

"I switched to a local version of prototypejs and added some debugging in the offending method (createWraper) but the debugging never appears before the error..."

Actually the offending function being called when the error occurs is "wrapper" which is created inside createWrapper (but not called there). Basically what is happening is that you've attached a function as the event handler for an element, and the function doesn't actually exist.

If you're trying to put any debug information in to try and pinpoint which function "doesn't exist" then add your alert messages or firebug console output inside the wrapper function between lines 3871 and 3878.

David McLaughlin
+3  A: 

I just found out this error also occurs if you accidentally leave on the parenthesis on your observer call:

Event.observe(document, 'myapp:application_ready', myapp.MyClass.initApp());

instead of

Event.observe(document, 'myapp:application_ready', myapp.MyClass.initApp);

A: 

nobighair: Sure, unless myapp.MyClass.initApp() returns a function object. :)

eyelidlessness
A: 

Thanks craing, exactly what I was looking for.