Help:Locating broken scripts

If you have problems with local gadgets or user scripts, these problems are often created by broken JavaScript code (the programming language that gadgets are written in) or undeclared dependencies on other code.

To track down the problematic code and place that needs fixing, you will have to use the developer tools of your web browser. This tool, combined with a special URL will help you to identify the broken scripts.

How-to
The following links explain how to do this for the following browsers: [https://developer.chrome.com/devtools Chrome/Chromium], [https://developer.mozilla.org/en-US/docs/Tools/Web_Console Firefox], [http://msdn.microsoft.com/en-us/library/ie/dn255006 Internet Explorer] and [https://developer.apple.com/library/mac/documentation/AppleApplications/Conceptual/Safari_Developer_Guide/Introduction/Introduction.html Safari].

After opening them, please append   to the web address (URL) of the page on which you see the problem. Example:  

If the URL does not already include a  . If the URL already includes a  , append  instead. Example:

For more technical information you can check toggle>ResourceLoader/Developing_with_ResourceLoader#Toggle_debug_mode</> how to Toggle debug mode (but you do not have to read that to follow the next steps.)

If there is a problem with JavaScript, an error should be printed in the 'console' of the developer tools.

Make sure that "JavaScript" or "JS" is enabled here, and potentially disable other output so the output does not get too noisy: