The query page is broken down into the following sections:

Bug Settings
People Involved
Text Search Options
Module Options
Advanced Querying
The Bottom Of The Form

"I already know how to use Bugzilla, but would like information about Bugzilla and the author of this document."
"Ok, I am almost certain the bug I discovered isn't in Bugzilla, how do I submit the bug?" - Read the guidelines first!

Back to the Query. If you typed anything in the forms already, you might want to hit back on the browser. When you are all done reading, do a sample query!

Status

• UNCONFIRMED - Nobody has validated that this bug needs to be fixed. Users who have the correct permissions may confirm this bug, changing its state to NEW. You can view your permissions here. A bug may be directly resolved and marked RESOLVED but usually a bug will be confirmed by the person to whom it is assigned. Usually, an UNCOMFIRMED bug will be left uncomfirmed until someone has verified that the bug the reporter submitted actually occurrs.
• NEW - This bug has recently been added to the assignee's list of bugs and must be processed. Bugs in this state may be accepted, and become ASSIGNED, passed on to someone else, and remain NEW, or resolved and marked RESOLVED.
• ASSIGNED - This bug is not yet resolved, but is assigned to someone who thinks they can fix it. From here bugs can be given to another person and become NEW, or resolved and become RESOLVED.
• REOPENED - The bug was once resolved, but the resolution was deemed incorrect. For example, a WORKSFORME bug is REOPENED when more information shows up and the bug is now reproducible. From here bugs are either marked ASSIGNED or RESOLVED.
• RESOLVED - A resolution has been made, and it is awaiting verification by the QA. From here bugs are either re-opened and become REOPENED, are marked VERIFIED, or are closed for good and marked CLOSED.
• VERIFIED- QA has looked at the bug and the resolution and agrees that the appropriate action has been taken.
• CLOSED - The bug is considered dead, the resolution is correct, and the product the bug has been reported against is terminated or shipped. Any zombie bugs who choose to walk the earth again must do so by becoming REOPENED. This state is rarely ever used.

Resolution

The resolution field indicates what happened to this bug.

No resolution yet: All bugs which are in one of the "open" states (meaning the state has no associated resolution) have the resolution set to blank. All other bugs will be marked with one of the following resolutions.

• FIXED - A fix for this bug is checked into the tree and tested.
• INVALID - The problem described is not a bug
• WONTFIX - The problem described is a bug which will never be fixed.
• LATER - The problem described is a bug which will not be fixed in this version of the product.
• REMIND - The problem described is a bug which will probably not be fixed in this version of the product, but might still be.
• DUPLICATE - The problem is a duplicate of an existing bug. Marking a bug duplicate requires the bug number of the duplicate and that number will be placed in the bug description.
• WORKSFORME - All attempts at reproducing this bug were futile, reading the code produces no clues as to why this behavior would occur. If more information appears later, please re-assign the bug, for now, file it.

Platform

The platform field is the hardware platform against which the bug was reported. Legal platforms include but are not limited to:

• All (happens on all platform; cross-platform bug)
  
• Macintosh
• PC
• Sun
• HP

Note: Selecting the option "All" does not select bugs assigned against all platforms. It merely selects bugs that occur on all platforms.

Operating System

The operating system field is the operating system against which the bug was reported. Legal operating systems include but are not limited to:

• All (happens on all operating systems; cross-platform bug)
• Windows 95
• Windows 2000
• Mac System 8.0
• Linux
• Other (Not in any of these OSes)
  

Note that the operating system implies the platform, but not always. For example, Linux can run on PC and Macintosh and others.

Priority

The priority field describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to prioritize their work. The priorities are from P1 (Most important) to P5 (Least important).

Severity

The Severity field describes the impact of a bug.

• Blocker - Blocks development and/or testing work.
  
• Critical - Crashes, loss of data, severe memory leak.
  
• Major - Major loss of function.
  
• Normal - This is the run of the mill bug.
  
• Minor - Minor loss of function, or other problem where an easy workaround is present.
  
• Trivial - Cosmetic problem like misspelled words or misaligned text.
  
• Enhancement - Request for enhancement.
  

To search for bugs associated with an email address:

• Type a portion of an email address into the text field.
• Click the checkbox for the fields of the bug you expect the address will be within.

You can look for up to two different email addresses. If you specify both, then only bugs which match both emails will show up. This is useful to find bugs that were, for example, created by Ralph and assigned to Fred.

You can also use the drop down menus to specify whether you want to match addresses by doing a substring match, by using Regular Expressions, or by exactly matching a fully specified email address.

In this section, you can enter values that are searched for in all the bugs (or whatever you limit the bugs to in other fields). You might want to look at Bugzilla Text Searching to see info on Regular Expressions and text searching. The box next to these fields decides how a match will be determined.

Bug summary

This lets you search the summaries. The summary is one line that attempts to sum up the bug.

A description entry

This lets you search comments. Comments can be added by anybody. Comments are the largest searchable area in most bugs. If you really want to find a lot of matches, search the comments.
Note:Because comments can get quite extensive in bugs, doing this particular type of query can take a long time.

Associated URL

This lets you search the url field. This contains the url of the web page the bug is about.

Status Whiteboard

This lets you search the bug's status whiteboard. The status whiteboard contains general information that engineers add.

Keywords

Name	Description
4xp	Navigator 4.x Parity bugs. A bug is a Navigator 4.x Parity bug if it occurs on Mozilla builds, but does not occur using the latest release of Netscape Communicator 4.x.
64bit	Porting issues specific to 64-bit platforms.
access	Bugs and enhancement requests related to making Mozilla accessible to users with disabilities and special needs.
adt1.0.0	Use this keyword to nominate bugs for fixing on the Netscape 1.0.0 release.
adt1.0.0+	This keyword will replace the adt1.0.0 nomination keyoword if the bug has been approved by the Netscape Application Delivery Team for fixing on the 1.0.0 branch.
adt1.0.0-	This keyword will replace the adt1.0.0 nomination keyword if the bug has been rejected by the Netscape Application Delivery team for fixing on the 1.0.0 branch.
approval	A bug which has a reviewed fix and is waiting approval for check in.
arch	Mozilla architecture issues - API cleanup, module restructuring and redesign, platform coherency"
assertion	A bug that triggers an assertion.
calendar	For bugs not in calendar-specific code which nevertheless have an impact on the Mozilla Calendar.
classic	For bugs which happen only with the classic Skin/Theme.
compat	Not a bug, but something so commonly misused on the internet that we should provide a work-around for it. i.e., we do it right, but older browsers get it wrong.
crash	A Critical Severity bug which causes a crash.
css-moz	Bug in Mozilla CSS extensions (or missing but required feature). Mozilla also implements a few extensions to CSS which we have needed for our themes.
css1	Bug in support for CSS1 properties (or missing but required feature), i.e. CSS properties that were first introduced as part of the Cascading Style Sheets, level 1 specification. (Note that CSS2 changed the specification for a few of these properties, so where there are differences, Mozilla will support the CSS2 interpretation of CSS1.) See: http://www.w3.org/TR/REC-CSS1
css2	Bug in support for CSS2 properties (or missing but required feature), i.e. CSS properties that were first introduced as part of the Cascading Style Sheets, level 2 specification. (Includes CSS positioning properties.) See: http://www.w3.org/TR/REC-CSS2/
css3	Bug in support for CSS3 properties , i.e. CSS properties that were first introduced as part of the Cascading Style Sheets, level 3 specifications. CSS3 is currently under development (i.e. experimental). Current updates at: http://www.w3.org/Style/CSS/current-work Note that these specifications are still at the DRAFT stage.
dataloss	For bugs which that do not crash, but do cause critical data loss.
dom0	Bug in our DOM Level 0 support. Bugs with this keyword should generally be in the DOM Level 0 component. There is no official DOM0 specification.
dom1	RFE for or bug in a feature of the DOM that was introduced in DOM Level 1. See: http://www.w3.org/TR/DOM-Level-1/
dom2	RFE for or bug in a feature of the DOM that was introduced in DOM Level 2. See: http://www.w3.org/TR/DOM-Level-2-Core/ http://www.w3.org/TR/DOM-Level-2-Views/ http://www.w3.org/TR/DOM-Level-2-Events/ http://www.w3.org/TR/DOM-Level-2-Style http://www.w3.org/TR/DOM-Level-2-Traversal-Range/
ecommerce	Use this keyword to track and increase the priority on the technical and evangelism work that is needed to get Mozilla working well with financial and commerce sites.
edt0.9.4	use this keyword to nominate embedding bugs for fixing on the 0.9.4 branch.
edt0.9.4+	this keyword will replace the edt0.9.4 nomination keyowrd if the bug has been approved by the Netscape embedding delivery team for fixing on the 0.9.4 branch.
edt0.9.4-	this keyword will replace the edt0.9.4 nomination keyword if the bug has been rejected by the Netscape embedding delivery team for fixing on the 0.9.4 branch.
edt0.9.9	use this keyword to nominate embedding bugs for fixing on the 0.9.9 branch.
edt0.9.9+	this keyword will replace the edt0.9.9 nomination keyowrd if the bug has been approved by the Netscape embedding delivery team for fixing on the 0.9.9 branch.
edt0.9.9-	this keyword will replace the edt0.9.9 nomination keyword if the bug has been rejected by the Netscape embedding delivery team for fixing on the 0.9.9 branch.
edt1.0.0	use this keyword to nominate embedding bugs for fixing on the 1.0 branch.
edt1.0.0+	this keyword will replace the edt1.0.0 nomination keyword if the bug has been approved by the Netscape embedding delivery team for fixing on the 1.0 branch.
edt1.0.0-	this keyword will replace the edt1.0.0 nomination keyword if the bug has been rejected by the Netscape embedding delivery team for fixing on the 1.0 branch.
embed	For bugs which are blockers for embedding developmental work.
evang500	Evangelism bugs for sites in the Evangelism top500.
fixed0.9.4	Use this keyword when you check in a fix to the 0.9.4 branch. QA will verify bugs with this keyword by adding the 'verified0.9.4' keyword.
fixed0.9.7	Use this keyword when you check in a fix to the 0.9.7 branch. QA will do branch verification of bugs with this keyword by testing the 0.9.7 branch and adding the 'verified0.9.7' keyword.
fixed0.9.9	Use this keyword when you check in a fix to the 0.9.9 branch. QA will do branch verification of bugs with this keyword by testing the 0.9.9 branch and adding the 'verified0.9.9' keyword.
fixed1.0.0	Use this keyword when you check in a fix to the 1.0.0 branch. QA will do branch verification of bugs with this keyword by testing the 1.0.0 branch and adding the 'verified1.0.0' keyword.
fixedSunBranch	Use this keyword when you check in a fix to the SUN_6_2_1_BRANCH. QA will verify bugs with this keyword by replacing it with 'verifiedSunBranch' keyword.
fonts	Bugs that are related to font styling, for instance text being drawn too large, not bold enough, a problem with the element in HTML or a problem with the 'font' properties in CSS.
footprint	Bugs addressing footprint/code size issues.
hang	Use this keyword for bugs which causes a Mozilla or system freeze (hang). Usually, this is a result of infinite loops. This is different than an application crash where a Talkback report is generated to help us isolate the bug.
helpwanted	Bugs or features which require coding assistance to fix or implement.
highrisk	Bugs whose fixes have a high level of risk associated with them, typically due to some major architectural changes being required (see the 'arch' keyword). Typically these are bugs that were deferred from the previous release cycle due to the high level of risk involved, and should therefore be fixed as soon as possible in the next cycle. Examples: "need to rewrite handling of HTTP headers" or "need to redesign the content sinks".
html4	Bug in support for HTML 4.0 only elements (whether required for compliance or not), i.e. HTML elements or attributes that were first introduced as part of the HTML 4.0 Specification, and not included in HTML 3.2
icon	Use this keyword to flag bugs which are ready for image production and visual design of icon or other artwork. Do not spam every feature request with this keyword. Thanks.
interop	Interoperability bugs (ie. with various IMAP mail servers)
intl	Use this keyword for any bug related to international issues. The keyword should be used when designating any international bugs other than the localizability bugs, marked by 'l12y'. The component name "internationalization" is used for i18n engineering bugs only and so it will constitute a sub-category of 'intl'. The 'intl' may also include those bugs that are not assigned to 'internationalization", e.g. layout, UI, browser, and other components, but have substantial international implication so that they can be monitored easily by those concerned about international issues.
js1.5	JavaScript 1.5 blocking bugs.
l12y	Use this keyword for any bug related to localizability issues like hardcoded strings, sizing information, hardcoded fonts...
mail1	Mail performance related bugs

Name	Description
mail2	Stability bugs. Bugs that when fixed contribute to reducing the Mean Time Between Failure.
mail3	Most important features. These will be features and or feature extensions. Examples are Usability bugs, UE Spec non-compliance bugs, threading, searching, import tools, filters, biff, improvements to the 3 pane window or compose window. (for use in bug triaging)
mail4	Important regressions. Regressions affecting high visibility/frequency tasks like reading and writing mail.
mail5	Important exceptions. Escalations, things outsides the target customer feature set, etc.
mail6	Low risk, high gain Mail bugs. Mail Bugs which require little engineering effort but have high user benefit that might not otherwise be covered under the other keywords.
mailtrack	Use this keyword on bugs which are filed in components besides MailNews which the Mail team needs to have fixed for rtm. Keyword used to track the bugs Mail team has nominated.
meta	A placeholder bug for tracking the progress of other bugs. Meta bugs are made dependent on other bugs so that interested parties can be kept up-to-date with status via one bug, without having to receive all the mails related to all the bugs related to the development of a particular area.
mlk	A memory leak bug - should be accompanied by a Purify (or equivalent) log in order to mark as a confirmed mlk bug.
modern	For bugs which occur with only the Modern theme included in Mozilla builds.
mozilla0.9.5	Add this keyword to propose that a bug must be fixed for mozilla 0.9.5. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla0.9.6	Add this keyword to propose that a bug must be fixed for mozilla 0.9.6. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla0.9.7	Add this keyword to propose that a bug must be fixed for mozilla 0.9.7. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla0.9.7+	drivers@mozilla.org would like to see these bugs checked in during the milestone freeze or branch period.
mozilla0.9.7-	drivers@mozilla.org do not consider these bugs critical for the 0.9.7 release. Please hold the fix until the tree opens for 0.9.8.
mozilla0.9.8	Add this keyword to propose that a bug must be fixed for mozilla 0.9.8. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla0.9.8+	drivers@mozilla.org would like to see these bugs checked in during the milestone freeze or branch period.
mozilla0.9.8-	drivers@mozilla.org do not consider these bugs critical for the 0.9.8 release. Please hold the fix until the tree opens for 0.9.9.
mozilla0.9.9	Add this keyword to propose that a bug must be fixed for mozilla 0.9.9. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla0.9.9+	drivers@mozilla.org would like to see these bugs checked in during the milestone freeze or branch period.
mozilla0.9.9-	drivers@mozilla.org do not consider these bugs critical for the 0.9.9 release. Please hold the fix until the tree opens for 1.0.
mozilla1.0	Add this keyword to propose that a bug must be fixed for mozilla 1.0. To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla1.0+	drivers@mozilla.org will add this keyword to bugs that have been evaluated as important to the Mozilla 1.0 release. This is not an approval for checkin during freezes. To get approval to check patches in please email drivers and look for the approval in the bug's patch status.
mozilla1.0-	drivers@mozilla.org will use this keyword to flag bugs that are not critical to a Mozilla 1.0 release.
mozilla1.0.1	Add this keyword to propose that a bug must be fixed for mozilla 1.0.1 To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla1.1	Add this keyword to propose that a bug must be fixed for mozilla 1.1 To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
mozilla1.2	Add this keyword to propose that a bug must be fixed for mozilla 1.2 To see whether a bug is likely to be fixed by this milestone check the Target Milestone setting in the bug.
nsbeta1	Use this keyword to nominate bugs for the next Netscape release.
nsbeta1+	The Netscape evaluation teams will add this keyword to bugs which have been accepted for the next Netscape release.
nsbeta1-	This keyword will be added to bugs which the Netscape evaluation team has rejected for the next Netscape release.
nsbranch	This indicates a bug has been nominated as a priority for the milestone branch targeted for a commercial version release. This keyword will be changed to nsbranch+ or nsbranch- per Netscape PDT triage of this bug.
nsbranch+	This indicates that Netscape PDT agrees that this bug represents a priority for the milestone branch targeted for a commercial version release. This bug will be scheduled into the milestone branch for the commercial version release.
nsbranch-	This indicates Netscape PDT does not agree that it represents a priority for the milestone branch targeted for a commercial version release.
nsCatFood	This indicates a bug nominated as a serious user satisfaction issue for Netscape releases. Look for this keyword to be changed to the nscatfood+ or the nscatfood- keyword by the Netscape review teams to indicate agreement or disagreement with the nomination. (CatFood is like DogFood, but for more finicky critters :-)
nsCatFood+	This indicates the review team for the bug agrees that it represents a serious user satisfaction issue with the product. This bug should be scheduled into the soonest possible milestone.
nsCatFood-	This indicates the review team for the bug does not agree that it represents a serious user satisfaction issue with the product. This bug should be scheduled normally based on its other attributes.
nsdogfood	This indicates a bug nominated as a blocker to using the product as dogfood. Dogfood is the ability for internal Netscape development to use the Seamonkey product for daily use. Look for this keyword to be changed to the dogfood+ or the dogfood- keyword to indicate Netscape PDT's approval/rejection of higher prioritization of this bug.
nsdogfood+	This indicates a bug accepted by the Netscape PDT as a blocker to using the product as dogfood. This bug has a higher than normal priority to be fixed.
nsdogfood-	This indicates a bug rejected by the Netscape PDT as a blocker to using the product as dogfood. This bug does not have a higher priority due to its dogfood nomination. (The bug's regular prioritization still applies.)
nsenterprise	This indicates a bug nominated as a blocker for Enterprise use. Enterprise use means the ability for large organizations (500+ users) to deploy the product for daily end-user use. This keyword will be changed to nsenterprise+ or the nsenterprise- keyword to indicate Netscape Enterprise Client Team (ECT) approval/rejection of higher prioritization of this bug.
nsmac1	Bugs that have a serious impact on Mac Netscape 6 and were "must fix" problems.
nsmac2	bugs that have a serious impact on Mac Netscape 6 and were "nice to haves".
nsonly	For bugs found only in the commercial (i.e. Netscape 6 PR1, Netscape 6 PR2, etc) builds and NOT in the mozilla builds.
oeone	used to flag bugs that have a direct impact on OEone products.
patch	Tracks contributions from the net community. Fixes/patches found by individuals without direct code check in privileges.
perf	A performance issue: optimizations, coping with large files, page loads, msg/folder load, etc.
polish	Bugs which require only a small change for a noticable improvement in the user interface
pp	Platform Parity bugs. A bug is a Platform Parity bug if it only occurs on one particular platform or two platforms, but not all three - Win, Mac and Linux. For example, if you find a bug on Linux, but it does not occur using the same day's Win32 or Mac OS build.
privacy	Bugs relating to user privacy which do not belong in the Security: General component.
qawanted	Use this keyword for bugs which need more info, or it needs reproducing, or testcasing, or it's a dupe but you can't find what it's a dupe of. Please remove this keyword when the wanted QA work has been completed.
realplayer	For bugs specific to incompatibilities with mozilla products and the RealNetworks' RealPlayer plugin .

Name	Description
regression	The problem was fixed, but then it came back (regressed) and this new bug was filed to track the regression. Also, for problems outside those identified in precheckin and smoke tests that were found in current builds that were known know to be working in previous builds. Tracking these bugs will help us to identify areas that are fragile, prone to bustage and are good candidates for adding to smoke and pre-checkin tests.
relnote	This bug need to be put on release notes for next milestone announcement.
relnote2	Use this keyword for bugs to release note for Netscape Beta2. These bugs are likely to occur to users which were not addressed for Beta2.
relnote3	Use this keyword for bugs to release note for Netscape Beta3. These bugs are likely to occur to users which were not addressed for Beta3.
relnoteRTM	Use this keyword for bugs to release note for Netscape RTM. These bugs are likely to occur to users which were not addressed for RTM.
review	A bug which has a fix and is waiting to be reviewed
scheduled	A bug which describes work included in some entity's scheduled activities. The distinguishing characteristic is that there is a plan in place that specifies a *date* when the work is projected to be complete. The best example of a "Scheduled" bug is a task bug that a feature tracking bug depends on.
sec508	This is used for bugs which keep us from being Section 508 accessibility regulation compliant (a requirement for Mozilla to be legally used by US Federal government agencies). See the requirements that apply to software.
shockwave	For bugs specific to incompatibilities with mozilla products and the MacroMedia Shockwave plug-in.
smoketest	Means that this bug prevents the smoketests from passing.
stackwanted	For crashing bugs which need stacktrace information to be added to description field to help out engineers debug the problem.
testcase	Indicates that a simplified test case is done and included in bug report. This keyword is used for the BugAThon: http://www.mozilla.org/newlayout/bugathon.html
top100	Bug with a top 100 site. Browser Buster Top 100 and other Top 100 lists
topcrash	Bugs created from highly visable crashes per the Talkback data.
topcrash+	This is an active topcrash bug, highly reproducible, a blocker for the average users, must be fixed before the release of the current Milestone. This keyword is administered by the topcrash team.
topcrash-	This is a topcrash bug that is either no longer highly visible to users, not reproducible, not in our code, or otherwise not critical to the release of the current Milestone. This keyword is administered by the topcrash team.
topembed	Use this keyword for bugs which are critical to embedding.
topembed+	The Netscape embedding evaluation team will add this keyword to bugs which have been accepted for the next Netscape embedding release.
topembed-	This keyword will be added to bugs which the Netscape embedding evaluation team has rejected for the next Netscape embedding release.
topmlk	A high profile memory leak bug - should be accompanied by a Purify (or equivalent) log in order to mark as a confirmed topmlk bug.
topperf	A high profile performance issue: optimizations, coping with large files, page loads, msg/folder load, etc.
ui	For bugs which need some attention for UI specific work to close out.
useless-UI	Use this keyword when the UI exposes a feature that is either unusably broken or not implemented. The purpose of this keyword is to make these UI shortfalls very visible when deciding whether or not the product is ready to ship. Example: "View|Headers|All does nothing so menuitem should be removed/hidden."
verified0.9.4	Use this keyword to mark a bug as Verified on the 0.9.4 branch.
verified0.9.7	Use this keyword to mark a bug as Verified on the 0.9.7 branch.
verified0.9.9	Use this keyword to mark a bug as Verified on the 0.9.9 branch.
verified1.0.0	Use this keyword to mark a bug as Verified on the 1.0.0 branch.
verifiedSunBranch	Use this keyword to indicate that a fix has been verified on the SUN_6_2_1_BRANCH.
verifyme	This bug is ok to verify with latest mozilla build by someone other than the QA Contact indicated. The bug has specific machine config indicated to verify fix. Try to reproduce the failure and if you agree that the resolution of Fixed is correct, please mark the Status as Verified. Always indicate the build/OS/platform(s) used to verify in the comments of the bug before you change Status to Verified. If the bug is reported on all three platforms and you only have one platform to verify the fix on, go ahead and do so and note it in the bug. But, do not mark the bug verified. All platforms must be checked before moving to a Verified Status. Finally, if other bugs have been marked as a duplicate of the bug you're verifying, be sure to check and mention those, as well. Often developers mark related, but not identical, bugs as duplicates, and these can fall through the cracks if not checked.
xhtml	Bugs related to support for XHTML

Module options are where you select what program, module and version the bugs you want to find describe. Selecting one or more of the programs, versions, components, or milestones will limit your search.

Products

Although all subprojects within the Mozilla project are similiar, there are several seperate products being developed. Each product has its own components.

Product Description Browser For bugs about the Mozilla Browser, including bugs with the New Layout project Browser Localizations For problems with translation, spelling and other errors in particular language packs and localized builds of Mozilla. Also for reporting browser bugs in languages other than english. Bugzilla For bugs in the Bugzilla Bug Tracking System (the code found at http://lxr.mozilla.org/mozilla/source/webtools/bugzilla). This is not the place to request configuration changes to this installation of Bugzilla. If you'd like to have keywords, components or initial owner/contact information changed, please file it under the appropriate component in the mozilla.org product below. Calendar For issues with the Mozilla Calendar product. CCK For bugs about the Client Customization Kit project Derivatives Sometimes bugs are reported to Bugzilla which are really bugs in a product that is derived from Mozilla and should be reported elsewhere. When you find such bugs assign them to this product to nominate them for transfer to the proper bug database. Do not file new bugs to this component. Examples: AIM or Net2Phone bugs in Netscape 6. Directory For bugs about the Directory (LDAP) project Documentation Documentation for Mozilla users, developers and web developers. Grendel For bugs about the Grendel java-based mail/news reader JSS Network Security Services for Java (JSS). A Java interface to NSS. MailNews For bugs about the Mozilla Mail/News project mozilla.org Tasks related to the running of the mozilla.org organization itself. MozillaClassic For bugs about the Mozilla web browser NSPR Netscape Portable Runtime library. libc and threading abstraction NSS Network Security Services (NSS) is a set of libraries designed to support cross-platform development of security-enabled server applications. NSS supports SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, X.509 v3 certificates and other security standsards. PSM Personal Security Manager (PSM), the module that performs all encryption and PKI in the browser, including SSL, TLS, and certificate management. Rhino A Java implementation of JavaScript Tech Evangelism For reporting web pages that must be upgraded to support web standards and Mozilla. Webtools For bugs about the web-based tools that mozilla.org uses. This includes LXR, Bonsai, and Tinderbox but does not include Bugzilla, which has its own product.

Version

This is simply the version that the bugs you want to find are marked for. Many of the bugs will be marked for another version and will have their milestones entered instead (milestones explained below).

Component

Each product has components, against which bugs can be filed. Components are parts of the product, and are assigned to a module owner. The following lists components and their associated products:

Component	Product	Description
Accessibility APIs	Browser	Description: This component relates to bugs in our support for accessibility APIs on the various platforms. Accessibility APIs allow 3rd party products, such as screen readers used by visually impaired users, to communicate with our content and UI. The APIs we will support specifically are MSAA on Windows and ATK on UNIX/Linux. Apple has not yet published specs for an accessibility API on OS X. This component is not for keyboard, focus or any accessibility bugs other than those relating to the APIs we export.
BiDi Hebrew & Arabic	Browser	Bugs related to Mozilla's implementation of bi-directional (BiDi) language support for Hebrew or Arabic
Bookmarks	Browser	Problems with the Bookmarks UI, including adding, deleting, editing. Also could include problems with Bookmarks Manager and Personal Toolbar.
Browser-General	Browser	A "catch all" component for problems found when using the Browser which do not fall into one of the current components. Example: launch/exit crashes, features missing, etc. PLEASE NOTE!! Try to find a component which is specific to your bug first - BEFORE assigning to this component!
Build Config	Browser	For bugs that result from Mozilla build problems. ("Building" is the process of converting the thousands of Mozilla source code files into a actual executable software.) If a file in a newly-downloaded build is missing or corrupted, file the bug in this component. Examples of appropriate bugs: Build date in browser window is incorrect; DLL files are missing from the ZIP file; or Build contains a zero K executable.
ChatZilla	Browser	An IRC client implemented with JavaScript and XUL.
Cookies	Browser	A general mechanism which server side connections (such as CGI scripts) can use to both store and retrieve information on the client side of the connection. This refers to HTML cookies; little blobs of data we store and share with sites
DOM Content Models	Browser	For bugs in our DOM Content Models, Validation and Load and Save support. This component deals with the DOM interfaces that test for well-formedness, perform content model (Schema and DTD) manipulation, and stream XML files to IO.
DOM Core	Browser	For bugs in our DOM Core support. This component deals with the DOM "Node" interface, the basic types like "DOMString", and related issues. Examples of appropriate bugs: DOMImplementation.hasFeature("Core", "2.0")returns false; Crash with setAttribute.
DOM Events	Browser	For bugs in our DOM Events support. This component deals with event bubbling, event handling, and interfaces such as UIEvent. Examples of appropriate bugs: cannot cancel 'submit' event; crash when handling a DOMNodeInserted event after inserting a node into anonymous content.
DOM HTML	Browser	For bugs in our DOM HTML support. This component deals with the HTML-specific DOM interfaces such as "HTMLOptGroupElement" and "HTMLLinkElement". Examples of appropriate bugs: changing HTMLLabelElement.accessKey has no effect; Crash with focus method on form elements.
DOM Inspector	Browser	The DOM Inspector is a tool used to examine, modify, and debug the DOM of HTML, XUL, or XML documents.
DOM Level 0	Browser	This component includes all functionality related to JavaScript manipulation of window, document and navigator objects that are available in Navigator 4.x and earlier, and that was never defined by the W3C.
DOM Mozilla Extensions	Browser	For bugs in our non-standard DOM support. This component covers areas such as XBL or XUL DOM methods and properties that do not fall under the XBL or XUL components.
DOM Other	Browser	For bugs in DOM support which do not fit into any other DOM Component
DOM Style	Browser	For bugs in our DOM Style and DOM CSS support. This component deals with the CSSStyleSheet interface, the "style" attribute, and so on. Examples of appropriate bugs: document.styleSheets doesn't hold missing file:// stylesheets; crash setting element.style.color to 'red'.
DOM to Text Conversion	Browser	Bugs involving conversion to html or plaintext, either during saving or during copy/paste. This component is NOT for general copy/paste bugs, for bugs involving save dialogs or writing to files when saving, or for I18n-related bugs; only for problems with the actual text which is saved.
DOM Traversal-Range	Browser	For bugs in our DOM Traversal and Range support. This component deals with the TreeWalker and DocumentRange interfaces, for instance. Examples of appropriate bugs: cloneContents() doesn't keep namespaces;NodeIterator crashes when calling nextNode() after calling detach().
DOM Viewer	Browser	For bugs against this test tool for viewing the structure of HTML and XML documents.
DOM Views and Formatting	Browser	For bugs in our DOM Views support. This component deals AbstractView and DocumentView interfaces. Examples of appropriate bugs: document.defaultView returns 'null'; calling document.defaultView.document crashes.
Download Manager	Browser	Provides a central manager for ongoing and finished downloads. Most bugs in this component will be the result of something you did from the download manager window.
Editor: Composer	Browser	For bugs in the Composer application, the high-level application that is used to create HTML documents. Appropriate bugs include those not belonging to the core editor engine, including an inability to launch the composer application and problems in the general user interface of the composer application or toolbar, such as incorrectly behaving toolbar buttons and menu items, and incorrect dialog behavior. Please see the bug description for Editor: Core for more information.
Editor: Core	Browser	For bugs in Mozilla's embeddable editor, If you're encountering a bug with text or rich text editing elsewhere within Seamonkey, such as within Mail/News, the URL bar, or a dialog box, file it here. Examples of appropriate bugs: After inserting a image, selecting Undo crashes Composer; or After deleting a word, the caret disappears.
Embedding: ActiveX Wrapper	Browser	This is the active-x wrapper that is used when people want to embed gecko in their application on windows. This is an external developer's code to wrap gecko up as an activeX control to replace IE as the embedded HTML control.
Embedding: APIs	Browser	The embedding API is the set of functions that an external application uses to host an instance of the layout engine within itself. The embedded layout engine provides services for rendering web content (HTML, XML, CSS, etc).
Embedding: Docshell	Browser	Previously Webshell. For bugs in the code functionality of Docshell.
Embedding: GTK Widget	Browser	A GTK widget that allows the embedding of Mozilla into GTK applications.
Embedding: Mac	Browser	Covers issues and bugs _specific to_ embedding in Mac carbon or cocoa applications.
Event Handling	Browser	Any strangeness with keyboard typing, mouse actions, focus changes.
File Handling	Browser	For issues dealing with helper applications, download UI and download management. This component does not cover: backend networking issues, such as those covered by Networking: FTP or Networking: File.
Form Manager	Browser	The component that captures user data appearing on a form and autofills that data on other forms. This component was previously known as "autofill".
Form Submission	Browser	This is HTML forms -- layout, rendering, functionality and submission.
GFX Compositor	Browser	Compositor (aka rendering) is for painting problems only. If the object is in the right place, but doesn't paint correctly, it's a rendering bug. If it paints ok, but in the wrong place, it's a layout bug. Rendering is for drawing problems. note: This is not the right place to file bugs on the HTML Composer. Please file Composer bugs on the Editor component.
Help	Browser	Use this component to report problems with the Help menu, Help menu items, and Help Viewer. Examples: Clicking a Help menu item fails to open the appropriate Help file; a Help document contains inaccurate information or typos; or Help Viewer missing buttons.
History: Global	Browser	This is the global history which tracks all URLs that a user has visited, across all sessions of the browser. This also includes the history window and link coloring. Examples of appropriate bugs: Chrome URLs incorrectly added to global history, Reproducible crash when sorting by Title in History window, misbehaviour in the History sidebar tab.
History: Session	Browser	This is the back/forward history for a particular browsing session. This includes bugs in HTML frame navigation and the navigator.history object. Examples of appropriate bugs: hitting Back or Forward does not take you to the expected page, dropdown lists from Back and Forward buttons are not accurate, crashes, slowness or bloat when navigating using Back and Forward.
HTML Form Controls	Browser	The XP library used by the layout engine for form controls. Think FORM elements: buttons, edit fields, etc.
HTMLFrames	Browser	This is HTML framesets -- layout and rendering. HTMLFrames == html frame/frameset/iframe tag handling.
HTMLTables	Browser	This is HTML Tables -- layout and rendering. Editing is applicable to most of the layout related categories, both Browser and Ender would use this component.
Image Conversion Library	Browser	The Image Conversion Library enables Mozilla's editor to convert Clipboard images from platform-native formats such as PICT and BMP to standard Web formats such as JPEG.
Image Management	Browser	For bugs about (un)blocking images from servers.
ImageLib	Browser	ImageLib decodes GIF, JPEG and PNG images, and provides the decoded data to the Compositor for display. If Seamonkey can display an image when loaded separately from the page, ImageLib is working, and the actual imaging bug exists elsewhere within Seamonkey. Please take a moment to learn how to submit useful ImageLib bugs before submitting bugs to this component. (If you need help assigning a particular imaging bug, we'll accept it in ImageLib and reassign it for you.) Examples of appropriate bugs: PNG gAMA chunk ignored; Crashes on GIF w/corrupted frame(merr-01.gif); or PNGs and JPEGs aren't displayed on FreeBSD.
Installer	Browser	For bugs in the native Mozilla installers, before Mozilla itself is running. Note: If the installer completes, but Mozilla (or the Mozilla User Profile Manager) won't launch or work correctly, this is not the right place to submit your bug; please try Browser-General. Examples of appropriate bugs: Install Wizard does not allow me to select installation directory; Crash during Installation; or Error message on install completion or cancel.
Installer: XPI Packages	Browser	For bugs in the actual .xpi installation modules used by the Mozilla installer. (An .xpi module is a compressed file containing the installation script and actual data files that the installer extracts and places onto your system.) Examples of appropriate bugs: Installer script in mail.xpi is defective; or .xpi module improperly built.
Installer: XPInstall Engine	Browser	For bugs in the underlying cross-platform installation technology used by the Seamonkey installers. If you encounter an installation failure via a web page, it probably belongs here. Content developers should also report failures of the XPInstall API to this component. Examples of appropriate bugs: Installer not installing all files; FinalizeInstall() doesn't check or return error codes; or Text from XPInstall confirmation dialog needs revision.
Internationalization	Browser	Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing the code needed.
Java APIs for DOM	Browser	A Java implementation of the Core DOM Level 1 Specification. This API allows Java Applets to access and manipulate the Gecko DOM.
Java APIs to WebShell	Browser	This component is for bugs against the java API wrapper around WebShell.
Java to XPCOM Bridge	Browser	For bugs with the interoperability between XPCOM components and Java objects.
Java-Implemented Plugins	Browser	For bugs against the support for Plugins that are written in Java. This is not OJI, nor the Java Plugin (formerly known as Activator)..

Component	Product	Description
JavaScript Console	Browser	The JavaScript Console displays JS errors, warnings and messages. This component is for problems with the Console itself and not for browser or web page problems that are noted in the console.
JavaScript Debugger	Browser	Bugs, problems, enhancements for the javascript debugger tool.
JavaScript Engine	Browser	The interpreter engine for the core JavaScript language, independent of the Mozilla browser and its object model. Used to embed the JavaScript language in a variety of applications. File ONLY core JavaScript language bugs in this category; file DOM, style bugs to the DOM Level 0 component.
Keyboard Navigation	Browser	Covers keyboard shortcuts, access keys/accelerators and navigation by using the keyboard (not the mouse or other input device). Examples: Ctrl+W not closing the browser window under win32. Command+N not opening a new browser window under Mac OS. Alt+[ not going to the previous page under linux. Alt not accessing the menu or access keys under win32. Also, the debate as to use Alt or Ctrl under linux as the keyboard control key for shortcuts. Requests for additional keyboard shortcuts.
Layout	Browser	Layout is for general problems with the positioning of objects on the page. If you can't tell specifically why an object seems to be in the wrong place, use layout.
Live Connect	Browser	LiveConnect is bridging code that connects the standard JavaScript API's with Java API's to provide interlanguage calling. Through LiveConnect Java can access and call objects in JavaScript and JavaScript can access and call public methods and data in Java objects.
Localization	Browser	Localization is the process of adapting software for a specific international market; this process includes translating the user interface, resizing dialog boxes, replacing icons and other culturally sensitive graphics (if necessary) as well as customizing features.
MathML	Browser	Mathematical Markup Language
MozillaTranslator	Browser	MozillaTranslator is a java based GUI tool, for helping with localizing mozilla.
Networking	Browser	For bugs in Mozilla's modular networking library (aka "Netlib" or "Necko".) The networking library supplies the software interface that Mozilla uses to access physical transports (e.g. the Internet and local drives), perform URL resolutions, and handle a variety of networking protocols. Examples of appropriate bugs: URLs with backslash not fetched; URLs starting with a single slash turn into http:///; or Cannot access authenticated FTP site.
Networking: Cache	Browser	For bugs in the cache, which stores recently accessed data for more rapid access. Includes the disk cache, memory cache, and all cache preferences. Examples of appropriate bugs: Implement compression of network cache data; or Implement partial HTTP caching.
Networking: File	Browser	For bugs in Mozilla's File IO code. This component deals with File specific issues like saving to disk, reading local files, etc Related problems with file:// protocol may also be addressed here.
Networking: FTP	Browser	For bugs in Mozilla's FTP code. This component deals with FTP specific issues like downloading, directory formats, problems with FTP login, or resuming partial downloads, etc Examples of appropriate bugs- Problems with multiple occurrences of files in directory listings , corruption in downloading certain files via FTP, etc
Networking: HTTP	Browser	For bugs in Mozilla's HTTP networking code. This component deals with HTTP specific issues like pipelining, keep-alive, HTTP proxies, 1.1 issues, redirects, authentication (basic), etc. Examples of appropriate bugs: Problems with proxy authentication; HTTP redirects looping indefinitely, etc.
OJI	Browser	Pluggable java API
Page Info	Browser	For issues with the Page Info window.
Parser	Browser	This system consumes content from the web, parses, validates and builds a content model (document)
Password Manager	Browser	The component that captures usernames/passwords and prefills them when the site is returned to. This component was previously known as "single signon"
PICS	Browser	Originally designed to help parents and teachers control what children access on the Internet, PICS (Platform for Internet Content Selection), is a W3C specification that enables labels (metadata) to be associated with Internet content. As of M14, Seamonkey is not expected to include PICS support, and the code has been removed from the Mozilla tree.
Plug-ins	Browser	Plugins allow 3rd parties to register a binary library to be called when a given mime datatype is encountered. The plugin can layout and render the datatype.
Preferences	Browser	For bugs that affect the Preferences window's user interface generally like ``no scrollbar in category pane'' use this component. Do not use this component for bugs in the *content* of specific preferences panes like ``typo in Navigator pref pane'' or ``radio buttons on Composer pref pane appear uninitialized''. Instead, file these sorts of bugs directly to the relevant component: use ``Editor: Composer'' in the last example. For more information on who to bug about preferences bugs please see: <http://www.mozilla.org/quality/browser/navigator-who2bug.html#prefs>
Preferences: Backend	Browser	For bugs in libPref, the backend library that reads, parses, and writes preferences to the user's hard disk. Unless you're a Mozilla developer, your bug probably doesn't belong in this component. Examples of appropriate bugs: prefs.js on the mac has non-mac style line endings; Large libpref string causes dialogs to crash on Linux; or JS Error at startup reading prefs file on migrated profile.
Print Preview	Browser	Problems in the rendering of Print Preview that are not seen when printing the same page.
Printing	Browser	Problems printing from this product should be submitted under this component.
Printing: Xprint	Browser	For bugs in Mozilla's X11 print system. Bugs in the postscript print system should be filed on the Printing Component and not here.
Profile Manager BackEnd	Browser	Problems with the creation, deletion and changing of user profiles during the installation process.
Profile Manager FrontEnd	Browser	Problems using the Profile Manager user interface.
Profile Migration	Browser	Problems with conversion from 4.x to 5.x profiles
QuickLaunch (AKA turbo mode)	Browser	For bugs related to the QuickLaunch installer option and preference, which keeps the app resident in memory after all windows are closed, to speed subsequent component loading.
RDF	Browser	Resource Description Framework: Core RDF components, including the in-memory datasource, composite datasource, RDF/XML parser, and RDF resource manager.
Search	Browser	For bugs associated with the Search button, the Search Results Sidebar panel, the Search menu (except for Find/Find in page...), and Advanced Search. For bugs involving the "Find" or "Find on Page..." menu items, use XPApps. Examples of appropriate bugs: Keyword searches should open Sidebar and show results; or Search button does not invoke dialog.
Security: CAPS	Browser	Caps is the capabilities-based security system for the browser. Manages principals (entities responsible for a piece of code) and the protected capabilities (the ability to perform a restricted action) that may be enabled for given principals.
Security: General	Browser	For non-crypto security bugs. Or use this general component if you know you have a Browser security bug, but not sure what component to use. Bug will be reviewed for proper component.
Selection	Browser	Selection refers to the user action of selecting all or part of a document and highlighting the selected content.
Sidebar	Browser	The Sidebar is a content area that holds a set of mini-webpages or data such as bookmarks or mail folders.
Skinability	Browser	Issues dealing with Theme Switching and the infrastructure/plumbing of skins. This subsumes the "skins" keyword. Example: Issues with the Themes Preference Panel, switching from one Theme to another, and skin interaction.
String	Browser	The hierarchy of classes related to managing character sequences.
Style System	Browser	Bugs in the handling of CSS stylesheets and the computation of style from CSS stylesheets and HTML attributes.
SVG	Browser	Bugs against the implementation of the Scalable Vector Graphics (SVG) specification. Reads and renders SVG content.
Tabbed Browser	Browser	problems in the browser tab features or problems with the widget itself.
Talkback	Browser	Problems related to the Full Circle client and server software.
Themes	Browser	Issues specific to the Classic or Modern themes. Example: Icons in Modern skin incorrect, behavior of Classic widget incorrect, etc.
Threading	Browser	Unlikely a tester would be able to tell there was a threading problem specifically. The result of threading problems are generally lock-ups. But unless you have a stack trace that specifically points the finger at threading, you should submit the bug against Browser-General.
Tracking	Browser	This component is used primarily for "tracking" bugs; bugs used to track a group of bugs.
URL Bar	Browser	This is the type-in history for the URL bar in the browser window. This includes behavior of the autocomplete widget for URLs, as well as the storage and expiration of the entries. Examples of appropriate bugs: URLs incorrectly added to the drop down list, crashes, hangs, slowness when using this feature.
User Interface Design	Browser	For usability issues in Mozilla's User Interface design. This is not the place to report broken or missing Mozilla features. Rather, this is where to raise specific issues and concerns regarding the quality of Mozilla's user interface design, and whether the implementation matches the design specifications. Before raising an issue here, you may wish to join netscape.public.mozilla.ui, where Mozilla community members discuss and resolve user interface issues. Examples of appropriate bugs: Edit location not tall enough {File>Open dialog}; or Mouseover effects should be optional for XPFE widgets.
Viewer App	Browser	This is the viewer test app. utilized by NG Layout engineers to test the layout engine.
Views	Browser	For bugs against the View System.
ViewSource	Browser	For issues concerning the source window for web pages. Examples of appropriate bugs: menu items in the view source window aren't working, unable to wrap lines in source window, coloring in source window is broken, etc. However, bugs dealing with the HTML Source tab in Composer and lower-level parsing issues do NOT belong here.
X-remote	Browser	X-Remote Client and Server
XBL	Browser	The Extensible Binding Language, used to bind new behavior and new content to XUL and HTML elements.

Component	Product	Description
XML	Browser
XP Apps	Browser	XP Apps is a broad category, so to avoid misfiling your bug, here are examples of what does not belong in this component: Helper application or downloading bugs. These should go to File Handling. Problems concerning plug-ins should go to Plug-ins. Practically an issue concerning the browser content area does NOT belong in XP Apps. For example, problems with how web pages are displayed (appearance, rendering) are unlikely to belong here --try Layout or one of the more specific HTML components. Similarly, problems with how images appear should probably go to ImageLib. Problems submitting a form should likely go to Form Submission. Likewise, issues with how form controls behave or appear belong in HTML Form Controls. Problems with the tabbed browser interface belong in Tabbed Browser. Problems with Java should probably go to OJI. Problems specific to a particular theme, eg, a bug in Modern but not Classic should be filed in Themes. Similarly, problems encountered after switching or installing themes belong in Skinability. Problems with UI/management of passwords belong in Password Manager. This component covers Mozilla's cross-platform, cross-application application framework. XP Apps would include bugs in the infrastructure of several dialogs, problems with the application logic, unless already covered by another component listed here on this page.
XP Apps: Autocomplete	Browser	Problems with autocompletion (e.g. behavior of the autocomplete widget) anywhere in the application. This includes autocomplete in the URLbar and mailnews address fields.
XP Apps: Cmd-line Features	Browser	For problems with command line parameter handling. Examples: mozilla -console doesn't work. mozilla -ProfileManager doesn't work. mozilla -turbo doesn't work.
XP Apps: Drag and Drop	Browser	Description: Problems with drag and drop functionality anywhere in the applications.
XP Apps: GUI Features	Browser	For problems with cross-platform applications that have a graphical interface. Make sure it doesn't fit into another, more applicable component before you file it here. Examples: View Page Source, Taskbar, Open Web Location dialog, Find in This Page, etc. doesn't work.
XP Miscellany	Browser	For cross-platform, code-level bugs that lack a more appropriate component. Examples of appropriate bugs: nsCString::Append(PRUnichar) ends up calling CopyChars2To2; or nsCString::Append(PRInt32 aInteger, PRInt32 aRadix) uses sprintf()
XP Toolkit/Widgets	Browser	XPToolkit includes a User Interface (UI) widget set consisting of menu bars and menus, toolbars and toolboxes, titled buttons, trees, tab widgets, scrollbars, splitters, progress meters, and boxes. Use this category for file picker, color picker, font picker and dialog/window bugs, too. XP Toolkit also accepts bugs relating to copy/paste, drag & drop, key bindings, the clipboard, and focus issues. All bugs concerning skins should use the "Skinability" component. User interface widgets that are part of a web browser's content (such as web forms) are actually handled by a separate toolbox --- rather than XP Toolkit --- and should be assigned to HTML Form Controls. Examples of appropriate bugs: Scroll bar disappears when you shrink window; Mouse wheel scrolling broken under Linux; or Horizontal scroll bar flickers mid-screen during window resize. NOTE: Please use "Keyboard Navigation" component for key cmd problems.
XP Toolkit/Widgets: Menus	Browser	For bugs in the cross-platform menu infrastructure, including the display and behavior of pop-up menus, pull-down menus, and context menus. (Pop-up menus that are part of a web page's content should be assigned to HTML Form Controls.) Examples of appropriate bugs: Command key symbol is missing from Mac menus; or Context menus pop up in wrong location.
XP Toolkit/Widgets: Trees	Browser	For bugs in the cross-platform tree widget. Examples of appropriate bugs: Scrolling w/arrow keys unpredictable in tree; Sorting tree when row selected causes crash; or Selecting an open tree item selects all of the children.
XP Toolkit/Widgets: XUL	Browser	For bugs in the XUL language. (XUL is an XML-based language which specifies Mozilla's user interface.) If you're not actually writing XUL code, this is probably not the right place for your bug. Examples of appropriate bugs: Duplicate window ID causes infinite loop; or Scrollbars disappear after loading XUL document
XPCOM	Browser	This is the basis of our component technology; this covers the mozilla/xpcom source directory and includes the "repository". Unlikely a tester would be able to tell there was an XPCOM problem specifically.
XPCOM Registry	Browser	The persistent registry used by xpcom.
XPConnect	Browser	Facilitates calling between JavaScript and XPCOM components.
xpidl	Browser	The tool that translates idl into xpcom header files and java script stubs.
XSLT	Browser	For bugs on Mozilla's XSLT support
Bosnian/bs-BA	Browser Localizations	Bosnian translation of Mozilla / Prevod Mozille na bosanski
Brazilian/pt-BR	Browser Localizations	Brazilian Portuguese translation of Mozilla (Tradução do Mozilla para Português do Brasil)
Bulgarian/bg-BG	Browser Localizations	Bulgarian translation of Mozilla / Ïðåâîä íà Mozilla íà áúëãàðñêè
Danish/da-DK	Browser Localizations	Danish translation of Mozilla. (Dansk oversættelse af Mozilla)
Dutch/nl	Browser Localizations	Dutch translation of Mozilla. (Nederlandse vertaling van Mozilla)
French/fr-FR	Browser Localizations	French translation of Mozilla. (Traduction française de Mozilla)
German-Austria/de-AT	Browser Localizations	German (Austria) translation & localization of Mozilla. (Deutsche (österreichische) Übersetzung von Mozilla)
Italian/it-IT	Browser Localizations	Italian translation of Mozilla. (Traduzione italiana di Mozilla)
Norwegian/nno-no	Browser Localizations	Norwegian (nynorsk) translation of Mozilla. (Norsk (nynorsk) omsetjing av Mozilla.)
Polish/pl-PL	Browser Localizations	Polish localization bugs
Administration	Bugzilla	Administration of a bugzilla installation, including editcomponents.cgi, editgroups.cgi, editkeywords.cgi, editparams.cgi, editproducts.cgi, editusers.cgi, editversions.cgi, sanitycheck.cgi
Bugzilla-General	Bugzilla	Anything that doesn't fit in the other components, or spans multiple components.
bugzilla.org	Bugzilla	The Bugzilla Project website (http://www.bugzilla.org/ or its mirror, http://www.mozilla.org/projects/bugzilla) and issues with any mailing lists served under the bugzilla.org domain. This component does not include The Bugzilla Guide.
Creating/Changing Bugs	Bugzilla	Creating, changing, and viewing bugs. enter_bug.cgi, post_bug.cgi, show_bug.cgi, process_bug.cgi
Documentation	Bugzilla	The bugzilla documentation, including anything in the docs directory and The Bugzilla Guide
Email Notifications	Bugzilla	Anything to do with email sent by Bugzilla. processmail
Installation & Upgrading	Bugzilla	The installation process of Bugzilla. This includes checksetup.pl and whatever else it evolves into
Query/Bug List	Bugzilla	Anything to do with searching for bugs and viewing the buglists. query.cgi and buglist.cgi
Reporting/Charting	Bugzilla	Getting reports from Bugzilla. reports.cgi, duplicates.cgi
Testing Suite	Bugzilla	The Bugzilla Test Suite, for finding problems with Bugzilla.
User Accounts	Bugzilla	Anything about managing a user account from the user's perspective. userprefs.cgi, saved queries, creating accounts, changing passwords, logging in, etc.
User Interface	Bugzilla	General issues having to do with the user interface cosmetics (not functionality) including cosmetic issues, HTML templates, etc
Calendar Front End	Calendar	For issues with the chrome, JavaScript, locale info and skin code which make up the Calendar front end.
Calendar General	Calendar	For issues which don't fit in a more specific Calendar component.
libical	Calendar	To track issues in the ical library from Software Studio.
libxpical	Calendar	For issues with the XPCOM wrapper for libical.
CCK-General	CCK	CCK bugs which do not fit into one of the other CCK components.
CCK-Installation	CCK	The CCK installation includes verifying the CD-layout. Other areas include the installations screens, directory structure, branding and launching the CCK Wizard.
CCK-Wizard	CCK	The CCK wizard allows the user to gather data by walking through a series of screens to create a set of customizations and build a media image.
Netscape 6	Derivatives	This component is for bugs found in items that are unique to Netscape 6. Sometimes bugs are reported to Bugzilla which are really bugs in Netscape 6. When you find such bugs assign them to this component to nominate them for transfer to Netscape's bug database. Do not file new bugs to this component. For instance AIM or Net2Phone bugs.
LDAP C SDK	Directory
LDAP Java SDK	Directory
LDAP Tools	Directory
LDAP XPCOM SDK	Directory	Software Development Kit for LDAP consisting of a number of XPCOM components and interfaces.
PerLDAP	Directory

Component	Product	Description
Mozilla Developer	Documentation	Information useful for people who compile mozilla.
User	Documentation	End-user documentation reachable from Mozilla's Help menu.
Web Developer	Documentation	Information useful to content creators, web site administrators, system administrators and people using Mozilla as an application development platform.
Addressbook/LDAP (non-UI)	Grendel
Preferences	Grendel
Protocols	Grendel
User Interface	Grendel
Documentation	JSS	documentation
Library	JSS	Library
Sample Code	JSS	Sample Code
Tests	JSS	tests
Account Manager	MailNews	Problems with setting up multiple mail and news accounts within a single profile in Mozilla Mail. A few examples: 1. User interface and functionality problems with the Account Manager and/or Account Wizard. 2. Managing multiple accounts such as deleting different accounts or adding them.
Address Book	MailNews	Problems with using the Address Book such as creating new cards, manipulating the data from the Address Book. Problems with importing to address books should also be reported in this component. A few examples: 1. User interface and functionality problems with the Address Book. 2. Trying to use the import tool such as importing or exporting address book cards.
Attachments	MailNews	For problems with mail or news message attachments.
BiDi Hebrew & Arabic	MailNews	Bugs related to Mozilla's implementation of bi-directional (BiDi) language support for Hebrew or Arabic
Composition	MailNews	Problems with the writing a new email or replying to one including using the autocomplete feature. Generally, problems found are within the compose window before sending a message. A few examples: 1. User interface and functionality problems with the html compose window and the plain text compose window. 2. Problems with addressing a mail message or adding an attachment.
Filters	MailNews	Problems with using filters to filter your mail. A few examples: 1. User interface and functionality problems with creating, editing, deleting, using filters. 2. Incoming mail is not filtered properly.
Internationalization	MailNews	Internationalization is the process of designing and developing a software product to function in multiple locales. This process involves identifying the locales that must be supported, designing features which support those locales, and writing code needed.
LDAP Mail/News Integration	MailNews	Problems with LDAP functionality that relate to mail/news components. For example, performing LDAP queries in the addressbook, LDAP typedown addressing/autocompletion, and LDAP preferences.
Localization	MailNews	Localization is the process of adapting software for a specific international market; this process includes translating the user interface, resizing dialog boxes, replacing icons and other culturally sensitive graphics (if necessary) and customizing features.
Mail Back End	MailNews	Problems with RDF data sources and application logic. Most likely, your problem can fit in one of the other components so this component should be rarely used.
Mail Database	MailNews	Problems with underlying code in storage of address book content and mail/news summary files. If the problem you are encountering is with the user interface of the address book or of accessing mail, then this component should not be chosen.
Mail Window Front End	MailNews	Problems with main mail window, standalone message window, sidebar contents, toolbars, dialogs, etc. A few examples: 1. User interface and functionality problems within the 3-pane mail window and the standalone message window.
MIME	MailNews	Problems with parsing the MIME structure and displaying messages. When this problem happens, it's often useful to attach a copy of the mail message generating the problem. If you have Communicator 4.x, you can select the message and save it as an .eml file (just save with the .eml extension). A few examples: 1. The contents of a message do not display properly. Certain items do not show up.
Movemail	MailNews	Problems with getting mail from the user's spool file. (/var/spool/mail/*). This is UNIX only.
Networking - General	MailNews	Problems with general networking issues integrating with libnet. For specific protocol problems, please choose: IMAP, News, POP, or SMTP from the list.
Networking - IMAP	MailNews	Problems with receiving mail when your mail account is set up for IMAP. This component should be chosen if you've verified that the receiving problem is specific to IMAP protocol. A few examples: 1. Interoperability problems with IMAP servers (ie. folders, naming conventions) would fall into this component. 2. Using the IMAP delete model
Networking - News	MailNews	Problems with posting to or reading newsgroups, adding news servers. If you are having problems adding a newsgroup or a news server, you should choose the "Subscribe" component from the list.
Networking - POP	MailNews	Problems with receiving mail when your mail account is set up for POP. This component should be chosen if you've verified that the receiving problem is specific to POP protocol. Deleting messages to the trash folder would also fall into this component.
Networking - SMTP	MailNews	Problems with sending mail. If you have specific problems with the compose window, you should choose the "Composition" component from the list.
Offline	MailNews	Problems with reading mail/news messages offline or related operations such as retrieving mail/news messages for offline use. Also includes problems with the offline UI menu items, etc.
Printing	MailNews	Problems with printing mail messages and address book cards.
Profile Migration	MailNews	Problems with migrating your profile from Communicator 4.x to the current Mozilla mail. Choose this component if you've verified that the problem you are seeing does not occur when you create a new profile and add the mail or news account you were using with migration.
Search	MailNews	Problems with using the Search functionality and user interface to search for mail messages, etc.
Security: General	MailNews	This component covers all bugs that relate to use of cryptography, S/MIME, and SSL issues for MailNews. Or, use this component if you have a MailNews security bug.
Simple MAPI	MailNews	File a bug against this component for problems when using the simple MAPI feature. This feature allows a non-messaging application to perform messaging operations, such as send, address, and receive messages.
Subscribe	MailNews	Problems with subscribing to newsgroups and adding news servers and problems with the Subscriber user interface.
Bugzilla: Keyword & Component	mozilla.org	File bugs here to request Keywords or Components be added or edited in mozilla.org's installation of Bugzilla. This is not the place to file bugs on Bugzilla itself.
Bugzilla: Other moz.org Issues	mozilla.org	This is the component for issues specific to bugzilla.mozilla.org that do not belong in other components. If you are not sure that it is a bugzilla.mozilla.org specific issue, then file the bug on Product Bugzilla instead.
CVS Account Request	mozilla.org	File a bug here to request CVS write access to the mozilla.org cvs repository. Before you file a bug, read our guide to getting CVS access.
FTP - Staging	mozilla.org	This component is for problems with stage.mozilla.org. This server hosted by sourceforge.net and is used for staging files which will be added to mozilla.org's ftp server at ftp://ftp.mozilla.org/
Miscellaneous	mozilla.org	Uncategorized things to do.
Server Operations	mozilla.org	System administration for the mozilla.org servers.
Tinderbox Platforms	mozilla.org	What Tinderbox platforms should be on the main page, and what should be on ports, and why. See http://www.mozilla.org/build/tinderbox-criteria.html. Up and coming platforms should be proposed and tracked via bugs filed in this component.
webmaster@mozilla.org	mozilla.org	For issues involving mozilla.org http servers and their content.
Aurora/RDF BE	MozillaClassic
Aurora/RDF FE	MozillaClassic
Berkeley DB	MozillaClassic
Browser Hooks	MozillaClassic
Calendar	MozillaClassic	These bugs used to live in the Calendar Product
Composer	MozillaClassic

Component	Product	Description
Compositor Library	MozillaClassic
FontLib	MozillaClassic
HTMLtoText/PostScript Trans	MozillaClassic
Java Stubs	MozillaClassic
JPEG Image Handling	MozillaClassic
Layout	MozillaClassic
LibMocha	MozillaClassic
Macintosh FE	MozillaClassic
MIMELib	MozillaClassic	Bugs in this area now assigned to MIME component in Mail/News product.
NetLib	MozillaClassic	Bugs in this area now assigned to Network Library component in Browser product.
PICS	MozillaClassic
PNG Image Handling	MozillaClassic
Preferences	MozillaClassic	Please see libPref, Pref UI or Profile Mgr components under Browser product for bugs against Preferences.
Registry	MozillaClassic
Security Stubs	MozillaClassic
StubFE	MozillaClassic
Windows FE	MozillaClassic
XFE	MozillaClassic
NSPR	NSPR	Cross-platform library providing runtime services, including threading, synchronization, File and Network I/O services, with a platform-independent API.
Build	NSS	Build system.
Documentation	NSS	NSS Documentation
Libraries	NSS	Libraries for client support of SSL v2 and v3, TLS, PKCS #5, PKCS #7, PKCS #11, PKCS #12, S/MIME, X.509 v3 certificates, and other security standards
Test	NSS	The QA test programs and the test driver scripts.
Tools	NSS	Tools to support NSS libraries
Client Library	PSM	PSM client library
Daemon	PSM	A daemon that performs cryptographic operations on behalf of a client application.
S/MIME	PSM	S/MIME is the sending of signed and/or encrypted email.
Compiler	Rhino	Java classfile generation and command-linecompiler tool.
Core	Rhino	Core JavaScript parsing, interpreter, runtime, and interactive shell.
African	Tech Evangelism	Evangelism bugs found on African sites or on sites which use an African language such as Bantu.
Asian	Tech Evangelism	Evangelism bugs found on Asian sites or on sites which use an Asian language. For this definition, Asian includes countries and languages of East, South and Southwest Asia. This category also includes languages like Mongolian and Tibetan.
Authors	Tech Evangelism	Web authoring programs (dreamweaver, frontpage, etc)
China	Tech Evangelism	This component is for filing bugs found in China. It is expected that the writing script of this component will be (Simplified) Chinese. Use GB2312 encoding to file your bugs if you are writing in Chinese.
English: Non-US	Tech Evangelism	English language sites in Canada, Australia, New Zealand.
Europe: Central	Tech Evangelism	All the Latin/Greek using countries of the Cental Europe, namely Poland, Lithuania, Latvia, Estonia, Czech Republic, Slovakia, Hungary, Romania, Greece, Slovenia, Croatia, Albania, Bosnia, etc.
Europe: East	Tech Evangelism	Former USSR countries like Russia, Ukraina, Armenia, Georgia, etc. plus Bulgaria, Yugoslavia, Macedonia, Serbia/Slavic Hercegovina.
Europe: West	Tech Evangelism	Countries/languages to the west of Germany's eastern border. This includes Germany, France, Austria, all Scandinavian countries, UK, Iceland, etc.-- i.e. what is commonly known as Western Europe.
Middle Eastern	Tech Evangelism	Evangelism bugs found on Israel, Egypt, Libya, Saudi Arabia, Iran, Iraq, etc. This category defines sites which use Hebrew or Arabic writing scripts no matter where they are located physically.
Pacific Islands	Tech Evangelism	Languages of the Pacific -- any of the languages classified under region/country names like Indonesia, Micronesia, Melanesia, Polynesia, etc.
Plugins	Tech Evangelism	Issues with web plugins not being compatible with Mozilla (quicktime, flash, shockwave, etc)
The Americas	Tech Evangelism	Evangelism bugs found on North, Central and South American sites. The sites in this cetgory use Spanish, Portuguese, Quechuan, or other languages of the Americas (except English) and are located in the above 3 regions. Spanish and Portuguese sites in Spain and Portugal should be classified under European.
US Banks	Tech Evangelism	Banks in the United States
US Ecommerce	Tech Evangelism	Ecommerce sites in the United States
US Edu	Tech Evangelism	Educational institutions in the United States
US General	Tech Evangelism	General component for United States sites that do not fit into some other more specific US component.
US Gov	Tech Evangelism	United States Government sites
Bonsai	Webtools	Web based Tree control system for watching the up-to-the-minute goings-on in a CVS repository
Bugzilla Helper	Webtools	A tool to help you write a good bug report.
Build	Webtools	Web based tool to help configure a browser build.
Despot	Webtools	mozilla.org's account management system
Doctor	Webtools	Doctor is a tool for editing documents on the mozilla.org website without using CVS.

Component	Product	Description
Litmus	Webtools	Litmus is a Testcase Management System. It is a way to document testcases, and track the outcome of running documented testcases.
LXR	Webtools	Source code cross reference system
Mozbot	Webtools	IRC robot that watches tinderbox and other things
Tinderbox	Webtools	Tree-watching system to monitor continuous builds that we run on multiple platforms.
Web Sniffer	Webtools	Web Sniffer is a set of tools to work with the protocols underlying the Web. Its main purpose is to let you see the HTTP headers returned by a web server

Milestone

Choosing this section lets you search through bugs that have their target milestones set to certain values. Milestones are kind of like versions. They are specific tentative dates where a massive phasing out of bugs occur and a relatively stable release is produced. For example, Mozilla.org had milestones in the form of "M10" or "M18", but now are in the form of "Mozilla0.9". Bugzilla milestones are in the form of "Bugzilla 2.12", "Bugzilla 2.14", etc.

Inclusion/Exclusion options is a powerful section that gives you the ability to include and exclude bugs based on values you enter.

[Only, Exclude] bugs numbered [text]

This lets you put in a comma-delimited list of bugs you want to have your results chosen from, or those of which you want to exclude. It would be nice in the future if you could type in ranges, i.e. [1-1000] for 1 to 1000. Unfortunately, you cannot do that as of now.

Changed in the last [text] days

Lets you specify how many days ago - at maximum - a bug could have changed state.

At least [text] votes

With this, you can choose how many votes - at minimum - a bug has.

Where the field(s) [fields] changed to [text]

With this, you can specify values to search for in fields that exist in the bug If you choose one or more fields, you have to fill out one of the fields to the right. It might be difficult to figure out what these fields mean if you are a newbie to the query. They match various fields within the bug information. Optionally, you can also enter what value you want the field to have changed to if you only entered one field. For instance, if the bug changed who it was assigned to from jon@netscape.com to brian@netscape.com , you could enter in assigned_to changed to brian@netscape.com.

During dates [text] to [text]

Here, you can choose what dates the fields changed. "Now" can be used as an entry. Other entries should be in mm/dd/yyyy or yyyy-mm-dd format.

The Bugzilla query page is designed to be reasonably easy to use. But, with such ease of use always comes some lack of power. The Advanced Querying section is designed to let you do very powerful queries, but it's not the easiest thing to learn (or explain).

The Advanced Query (or Boolean Chart) starts with a single "term". A term is a combination of two pulldown menus and a text field. You choose items from the menus, specifying:

Field 1: Where to look for the search term
Field 2: How to determine what is a match
Field 3: What the search term is

The real fun starts when you click on the "Or" or "And" buttons. If you push the "Or" button, then you get a second term right under the first one. You can then configure that term, and the result of the query will be anything that matches either of the terms.

You can push the "And" button, and get a new term below the original one - seperated by the word "AND", and now the result of the query will be anything that matches both sets of terms.

You can keep clicking "And" and "Or", and get a page with many terms. "Or" has higher precedence than "And". You can think of the lines of "Or" as having parenthesis around them.

The most subtle thing to notice is the "Add another boolean chart" button. This is almost the same thing as the "And" button. You want to use this when you use one of the fields where several items can be associated with a single bug - including: "Comments", "CC", and all the "changed [something]" entries. If you have multiple terms that all are about one of these fields (such as one comment), it's ambiguous whether they are allowed to be about different instances of that field or about only that one instance. So, to let you have it both ways, they always mean the same instance, unless the terms appear on different charts.

For example: if you search for "priority changed to P5" and "priority changed by person@addr", it will only find bugs where the given person at some time changed the priority to P5. However, if what you really want is to find all bugs where the milestone was changed at some time by the person, and someone (possibly someone else) at some time changed the milestone to P5, then you would put the two terms in two different charts.

So you have gotten all that down, but "What is this junk at the bottom of the form?" You can remember the current query as the default query page that is pulled up whenever you are logged on. There is also an ability to choose how you want your results sorted. When finished, click "Submit".

Written and adapted from some older Bugzilla documents (by Terry Weissman, Tara Hernandez and others) by Brian Bober You can talk to me on irc.mozilla.org - #mozilla, #mozwebtools, #mozillazine, I go by the name netdemon.

Lots of Bugzilla use documention is available through Mozilla.org and other sites:
How To Find Previously Reported Bugs
Bugzilla General Information
Mozilla Bug Report Form
Bugzilla Text Searching
The Bug Reporting Guidelines

My main motive for writing this was to help the engineers by giving new Bugzilla users a way to learn how to use the Bugzilla Query form. I had done a rewrite of query.cgi, so I said, "What the heck, I'll write this too".

You probably looked at the Query page and said, "This page looks too difficult. Now that I think about it, I don't really need to do a query". It is important to make sure that a bug doesn't have a duplicate before submitting it, as is stated clearly in The Bug Reporting Guidelines. The people reading your bugs are busy and usually swamped with bugs. Therefore, you are doing everyone a huge favor to search for a duplicate.

Ok. So lets find a bug! We'll borrow the Mozilla.org database because it's handy.
First, lets make a copy of the query window so you can easily switch between this document and the query.

Do the following:

• Go to the "Status" field in and select all fields (or deselect all fields).
• In Text Search options, put Autoscroll in the summary and Panning in the description entry box (meaning that panning is somewhere in the comments and the bug's summary has Autoscroll in it).

One of the results should have been bug 22775 - [RFE] AutoScroll/Panning support...