Wikipedia:Reporting JavaScript errors

Info to include in bug reports

When you experience an error with gadgets or user scripts and you want to report the issue at the appropriate page, please include the following information:

1. What is the behaviour you're seeing?
2. What is the behaviour you're expecting to see?
3. How can the incorrect behaviour be reproduced? Describe exactly what you're doing and seeing.
4. Confirm that you have tried bypassing your browser cache.
5. Make note of the skin that you use, your browser, browser version, and operating system.
6. Mention relevant JavaScript errors your browser logged. To do that, open your JavaScript console, and copy the relevant error messages. Error messages usually appear in red.

You are urged to have a look at "How to Report Bugs Effectively" by Simon Tatham for hints on how to report bugs effectively, to make sure the issue you are describing can be resolved as promptly as possible.

How to open your JavaScript console

Where to find your JavaScript console depends on your browser:

How to open the console

Computer	Browser	Windows/Linux	Mac
Desktop/Laptop	Chrome/Chromium Edge (version 79 ) Opera (version 15 )	Ctrl ⇧ Shift J	⌥ Option ⌘ Command J
	Firefox	F12	⌥ Option ⌘ Command K
	Safari	Ctrl Alt C	⌥ Option ⌘ Cmd C*
	Internet Explorer Edge (up to version 78)	F12 → Console	–
	Opera (up to version 14)	Page menu → Developer Tools → Error Console
Tablet/Mobile	Mobile operating systems do not usually have developer tools or consoles. However, some mobile browsers support remote debugging, where you connect your mobile device to a desktop via USB, and then you can access developer tools/consoles that way. Firefox USB debugging. Chrome USB debugging.

On some browsers, you may have to click on the "Console" tab once the developer tools pane opens up.

[*] In Safari, you might have to enable the Develop menu first in Preferences (⌘ Cmd ,) → Advanced → check "Show develop menu in menu bar". For OSX, use ⌥ Option ⌘ Command I then hit esc (escape) to open the JavaScript console. Errors will appear in red.

Once you've opened the console...

Google Chrome DevTools, Console tab

The "triangle" can be clicked to reveal some hidden info.

1. Click on the "Console" tab
2. Scroll to the bottom of the console and look for log entries in yellow and red. Copy or screenshot these.
3. If there is a "triangle" you can press to expand and show more info, do so, and copy/screenshot that info too.

Which one is the error?

Unfortunately there is a lot of junk in the console. Programmers really only need one error message to debug, but the trick is getting the right error message. Here's some examples of useful error messages:

• Uncaught – typically red
  • Uncaught DOMException
  • Uncaught Error
  • Uncaught ReferenceError
  • Uncaught SyntaxError
  • Uncaught TypeError
  • Uncaught (something in all lowercase)
• jQuery exception – typically yellow
  • jQuery.Deferred exception

See also

• mw:Help:Locating broken scripts