Step 2 of 3 - give information

If you've tried a few searches and your bug really isn't in there, tell us all about it.

Product Firefox
Component
For bugs in Firefox which do not fit into other more specific Firefox components

The area where the problem occurs. To pick the right component, you could use the same one as similar bugs you found in your search, or read the full list of component descriptions (opens in new window) if you need more help.

Hardware Platform
Operating System
Build Identifier

This should identify the exact version of the product you were using. If the above field is blank or you know it is incorrect, copy the version text from the product's Help | About menu (for browsers this will begin with "Mozilla/5.0..."). If the product won't start, instead paste the complete URL you downloaded it from.

URL

URL that demonstrates the problem you are seeing (optional).
IMPORTANT: if the problem is with a broken web page, you need to report it a different way.

Summary

A sentence which summarises the problem. Please be descriptive and use lots of keywords.

Bad example: mail crashed
Good example: crash if I close the mail window while checking for new POP mail

Details

Expand on the Summary. Please be as specific as possible about what is wrong.

Bad example: Mozilla crashed. You suck!
Good example: After a crash which happened when I was sorting in the Bookmark Manager,
all of my top-level bookmark folders beginning with the letters Q to Z are no longer present.

Reproducibility
Steps to Reproduce

Describe how to reproduce the problem, step by step. Include any special setup steps.

Actual Results

What happened after you performed the steps above?

Expected Results

What should the software have done instead?

Additional Information

Add any additional information you feel may be relevant to this bug, such as the theme you were using (does the bug still occur with the default theme?), a Talkback crash ID, or special information about your computer's configuration. Any information longer than a few lines, such as a stack trace or HTML testcase, should be added using the "Add an Attachment" link on the bug, after it is filed. If you believe that it's relevant, please also include your build configuration, obtained by typing about:buildconfig into your URL bar.

If you are reporting a crash, note the module in which the software crashed (e.g., Application Violation in gkhtml.dll).

Security

Severity

Say how serious the problem is, or if your bug is a request for a new feature.

Step 3 of 3 - submit the bug report

That's it! Thanks very much. You'll be notified by email about any progress that is made on fixing your bug.

Please be warned that we get a lot of bug reports filed - it may take quite a while to get around to yours. You can help the process by making sure your bug is complete and easy to understand, and by quickly replying to any questions which may arrive by email.