Firefox 11 Security Error? How to track it

Question

Today, Firefox 11 pushed the release channel, and to my chagrin, one of the third-party libraries that I use on our Intranet (in particular, the Hookbox) now launches a "Security Error" on the console when it starts. For some reason, the library uses many unconditional () the insanities (which I never liked) that I think make it a little harder to track.

Is there anything I don’t know in Firefox that will help me figure this out faster? The piece of code that it highlights as causing the error does not really make any sense. It would be helpful if I knew exactly what type or cause of the security error, for example.

I am not asking for help to sort out my specific problem, but I was hoping that Firefox had information about Javascript security errors in general.

Answer 1

You can wrap the violation code in a try / catch block, then in the catch section you can either console.log () or console.dir () the error object passed to the catch section. For instance:

try { security_error(); } catch(error_obj) { console.log(error_obj); } 

Error_obj member variables should contain more information about the actual error.