Why should you use this?

This form prompts you for information that is essential to Mozilla developers. They need this information to understand and reproduce the bug. Being able to understand and reproduce bugs is the first step towards getting the bug fixed.

This form currently requires a browser that supports JavaScript1.2 or greater, and that JavaScript is turned on.

Step 1. Create a Bugzilla account and log in.

Create a Bugzilla account if you don't already have one. After you receive your Bugzilla password, log in if you haven't already logged in.

Step 2. Search for your bug.

See if your bug has already been reported. Check the list of most frequently filed bugs. If you don't find your bug, then search Bugzilla here. Enter two or three of the main words having to do with your bug. For example: crash mail or copy paste

Search Bugzilla
	Only Look in Summary Fields Look in both Summary and Description Fields

Look through the search results. If you get the cryptic Zarro Boogs message, Bugzilla found no bugs that match. Check for typos, or add fewer or different keywords.

If you find a bug that looks the same as yours, you can add comments to that bug, but please don't open a new one.

If you find bugs similar to yours, read them. Note their Component; you'll need it later.

Step 3. Gather information.

Please try to complete this form as accurately as you can. The more you can tell us, the better our chance of being able to understand and reproduce your bug.

Product	Browser or Editor (aka Composer) Mail or News Documentation
Component	Choose one... ActiveX WrapperAutofillBookmarksBrowser-GeneralBuild ConfigchatzillaCompositorCookiesDOM Level 0DOM Level 1DOM Level 2DOM to Text ConversionDOM ViewerEditorEmbedding APIsEmbedding: DocshellEvent HandlingForm SubmissionGTK Embedding WidgetHelpHistoryHTML ElementHTML Form ControlsHTMLFramesHTMLTablesImage Conversion LibraryImageLibInstallerInstaller: XPI PackagesInstaller: XPInstall EngineInternationalizationJava APIs for DOMJava APIs to WebShellJava FrontEndJava to XPCOM BridgeJava-Implemented PluginsJavaScript DebuggerJavascript EngineLayoutLive ConnectLocalizationMathMLMozillaTranslatorNetworkingNetworking: CacheOJIotherParserPICSPlug-insPreferencesPreferences: BackendPrintingProfile Manager BackEndProfile Manager FrontEndProfile MigrationProgress WindowRDFSearchSecurity: CAPSSecurity: CryptoSecurity: GeneralSelectionSidebarSingle SignonStyle SystemSVGThreadingUser Interface: Design FeedbackViewer AppViewsXMLXP MiscellanyXP Toolkit/WidgetsXP Toolkit/Widgets: MenusXP Toolkit/Widgets: TreesXP Toolkit/Widgets: XBLXP Toolkit/Widgets: XULXP UtilitiesXPAppsXPCOMXPCOM RegistryXPConnectxpidlY2k This is the hard part. Here are some tips on picking the right component. Read the MailNews and Browser component descriptions, and try to pick the best component for your bug. Go back to Step 2. Search for bugs that are similar to yours, and put yours in the same Component. If you can't decide, select a component from the list above, and click the button to see the bugs in that component. Decide if your bug fits in that group.
Platform	Choose One...AllDECHPMacintoshPCSGISunOther
Operating System	Choose One...AllWindows 3.1Windows 95Windows 98Windows 2000Windows NTMac System 7Mac System 7.5Mac System 7.6.1Mac System 8.0Mac System 8.5Mac System 8.6Mac System 9.0AIXBSDIHP-UXIRIXLinuxFreeBSDOSF/1SolarisSunOSNeutrinoOS/2BeOSOpenVMSother
Build ID	This is the number in the lower right hand corner of your Browser window.
URL	URL that demonstrates the problem you are seeing.
Summary Please be descriptive and use lots of keywords.	Examples: Bad: mail crashed Good: crash if i close the mail window while checking for new POP mail
Description Expand on the Summary. Please be as specific as possible about what is wrong.	Examples: Bad: This page looks wrong in Mozilla. Other browsers display it correctly. Good: In the page at http://www.foo.com/, text in the first column should be fully justified -- text should be aligned with both the left and right margins. In Mozilla, the text is only left-justified.
Reproducibility How often can you reproduce the problem?	Choose one... Every time. Sometimes, but not always. Haven't tried to reproduce it. Tried, but couldn't reproduce it.
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 Mozilla have done instead?
Additional Information Add any additional information you feel may be relevant to this bug, such as a few lines of HTML that demonstrate the problem, a Talkback crash ID, or special information about your computer's configuration. If you are reporting a crash, note the module in which Mozilla crashed (e.g, application violation in gkhtml.dll). If you can provide a stack trace, paste that information here. On Macintosh, if you have MacsBug, paste the results of the how and sc commands.
Severity	Blocker: This bug prevents you from being getting Mozilla testing or development work done. Critical: Mozilla crashes, hangs, leaks memory, or causes you to lose data. Major: A major feature is broken. Normal: It's a bug that should be fixed. Minor: Minor loss of function, and there's an easy workaround. Trivial: A cosmetic problem, such as a misspelled word or misaligned text. Enhancement: Request for new feature or enhancement.

Check out the Bugzilla Fact Sheet's Life Cycle of a Bug section to see what will happen to your bug.

Thanks for making the effort to file a good bug!