Uncaught Exceptions

Today I isolated a particularly frustrating bug. During the event creation process, clicking on any form field was producing an “uncaught exception” in FireFox.

uncaught exception: Permission denied to get property HTMLDivElement.parentNode

I finally isolated the problem to be coming from Matt Kruse’s Calendar Popup but could not, for the life of me, figure out what was causing it or how to get rid of it. Luckily, I remembered that I had seen the same calendar on MyPunchbowl, so I ran over there and grabbed their copy of the javascript file. I’m not sure what they did to it, but it’s no longer throwing errors. Thanks, MyPunchbowl!

This entry was posted on Sunday, July 8th, 2007 at 10:25 am and is filed under Bugs. You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

8 Responses to “Uncaught Exceptions”

  1. Jay Vincent Says:
    July 25, 2007 at 6:30 am

    I had the same problem. After running windiff on the original version against mypunchbowls problem, I came across a slight difference which accounted for the error.

    Original:
    var t = e.originalTarget;

    Mypunchbowl:
    var t = e.target;

    What exactly the change is doing I can’t really make out though… I’m just glad its fixed!

  2. Dr. Alabaster Says:
    August 1, 2007 at 11:05 am

    The formatting in punchbowl’s version is so vastly different that my unix diff really doesn’t tell me much. Thanks for nailing this one guys, the calendar is good but I almost had to ditch it for something less sexy.

  3. steve Says:
    September 13, 2007 at 8:40 am

    thanks so much for the fix. works great

  4. John Says:
    October 27, 2007 at 2:16 am

    wow… thank you so much! i introduced the new calendar while also doing some autocomplete stuff and I was sifting through the scriptaculous code to try and find the event that isn’t catch it’s own exception. such a time saver!!

    still can’t get the darn textbox to focus the cursor, but that’s a much smaller problem to solve. (if you know the solution for this as well please feel free to ping me)

    cheers!!

    john

  5. Kevin Says:
    March 5, 2008 at 11:06 pm

    thanks for the fix. I spent 6 months wondering where I was getting this error from.

  6. FLUID Says:
    April 24, 2008 at 10:23 am

    Thanks for very very helpful post! I’ve finally fixed this annoying bug in my JS!
    Cheers!

  7. Scott Says:
    May 5, 2008 at 11:55 am

    Thanks! This worked for me as well! It took some time to find this solution. I didn’t even recognize that is was because of the calendar. Luckily I only spent a few hours on this issue thanks to this post!!!!

  8. ReofWooxom Says:
    August 3, 2008 at 2:09 pm

    I agreed with you

Leave a Reply