Hide inactive keywords

Name Description Active Open Bugs Total Bugs
64bit Porting issues specific to 64-bit platforms. Yes Search 370
access Bugs and enhancement requests related to making Mozilla accessible to users with disabilities and special needs. Yes Search 5787
addon-compat Used to indicate bugs which may affect compatibility of extensions or external code developed earlier in a cycle. Yes Search 1142
APIchange For flagging changes in APIs. Yes Search 70
arch Mozilla architecture issues: API cleanup, module restructuring and redesign, platform coherency. Yes Search 736
assertion A bug that triggers an assertion. Yes Search 9254
ateam-b2g-big Bugs related to large A*Team B2G tasks Yes Search 1
ateam-b2g-device-big Bugs related to large A*Team B2G on-device tasks Yes Search 5
ateam-b2g-device-goal Bugs related to A*Team B2G on-device goals Yes Search 2
ateam-b2g-device-task Bugs related to smaller A*Team B2G on-device tasks Yes Search 5
ateam-b2g-goal Bugs related to A*Team B2G goals Yes none none
ateam-b2g-perf-big Bugs related to large A*Team B2G performance tasks Yes none none
ateam-b2g-perf-goal Bugs related to A*Team B2G performance goals Yes none none
ateam-b2g-perf-task Bugs related to smaller A*Team B2G performance tasks Yes Search 4
ateam-b2g-task Bugs related to smaller A*Team B2G tasks Yes Search 12
ateam-community-big Bugs related to large A*Team community tasks Yes none none
ateam-community-goal Bugs related to A*Team community goals Yes Search 3
ateam-community-task Bugs related to smaller A*Team community tasks Yes none none
ateam-datazilla-big Bugs related to large A*Team datazilla tasks Yes Search 1
ateam-datazilla-goal Bugs related to A*Team datazilla goals Yes none none
ateam-datazilla-task Bugs related to smaller A*Team datazilla tasks Yes Search 3
ateam-desktop-perf-big Bugs related to large A*Team desktop performance tasks Yes none none
ateam-desktop-perf-goal Bugs related to A*Team desktop performance goals Yes Search 1
ateam-desktop-perf-task Bugs related to smaller A*Team desktop performance tasks Yes none none
ateam-marionette-big Bugs related to large A*Team marionette tasks Yes Search 3
ateam-marionette-client All bugs related to the marionette client binding Yes Search 102
ateam-marionette-displayed All bugs that related to how marionette interprets element displayed state Yes Search 20
ateam-marionette-docs All bugs related to Marionette documentation Yes Search 7
ateam-marionette-goal Bugs related to A*Team marionette goals Yes Search 19
ateam-marionette-httpd Relates to all issues to do with the Marionette httpd as required by the webdriver specification Yes Search 5
ateam-marionette-intermittent All intermittent bugs in Marionette unit tests Yes Search 209
ateam-marionette-runner Bugs that relate to how marionette tests are run from b2g to desktop Yes Search 133
ateam-marionette-server Issues relating to the gecko side of Marionette Yes Search 294
ateam-marionette-spec All bugs related to implementation and bugs in implementation of the WebDriver specification Yes Search 47
ateam-marionette-task Bugs related to smaller A*Team marionette tasks Yes Search 13
ateam-marionette-transport All issues related to marionette transportation module Yes Search 1
ateam-marionette-userinput All bugs that relate to how marionette emulates user input Yes Search 45
ateam-mobile-big Bugs related to larger A*Team mobile tasks Yes Search 1
ateam-mobile-goal Bugs related to A*Team mobile goals Yes none none
ateam-mobile-perf-big Bugs related to large A*Team mobile performance tasks Yes none none
ateam-mobile-perf-goal Bugs related to A*Team mobile performance goals Yes none none
ateam-mobile-perf-task Bugs related to smaller A*Team mobile performance tasks Yes none none
ateam-mobile-task Bugs related to smaller A*Team mobile tasks Yes none none
ateam-perf-big Bugs related to large A*Team performance tasks Yes none none
ateam-perf-goal Bugs related to A*Team performance goals Yes none none
ateam-perf-task Bugs related to smaller A*Team performance tasks Yes Search 1
ateam-summer-of-contribution Bugs related to the ateam summer of contribution initiative Yes Search 19
ateam-talos-big Bugs related to large A*Team talos tasks Yes Search 2
ateam-talos-goal Bugs related to A*Team talos goals Yes none none
ateam-talos-task Bugs related to smaller A*Team talos tasks Yes Search 11
ateam-unittests-big Bugs related to large A*Team unittests tasks Yes Search 3
ateam-unittests-goal Bugs related to A*Team unittests goals Yes Search 1
ateam-unittests-task Bugs related to smaller A*Team unittests tasks Yes Search 5
autoland Triggers the autolander robot to land a patch or github pull request. Must be used on patches attached by autolander. https://github.com/mozilla/autolander Yes Search 3
autotest-issue A bug whose presence materially impedes development or deployment of automated tests, or a capability whose addition would materially improve such. A bug marked with this keyword should Block at least one bug describing a relevant test affected by this bug. Yes Search 43
b2g-testdriver bugs filed by participants in the B2G Test Driver pre-release testing program Yes Search 738
bmo-big bugzilla.mozilla.org team request taking more than one day. Yes Search 25
bmo-goal bugzilla.mozilla.org team quarterly goal Yes Search 37
branch-patch-needed Bugs where a release is blocked on a branch-specific patch being created. Yes Search 18
bugzilla-rfc Bugzilla Request For Comments Yes none none
buildapi For bugs related to Release Engineering's Buildbot BuildAPI (more info) Yes Search 133
calendar-integration Used for Thunderbird bugs that would have benefit for calendar (i.e., adding ids, great features that would improve user experience) Yes Search 49
cert-waiver Bugs that have been waived from past certification test cycles for Firefox OS. Yes Search 5
checkin-needed Keyword to use to get a patch checked in, if you can't check it in yourself. The default assumption should be trunk; if something different is needed, special checkin instructions should go in the status whiteboard. Yes Search 19
china-p1 Top priority issues for Mozilla China Yes Search 5
china-p2 High priority issues for Mozilla China Yes Search 8
cisco-spark Cisco Spark related bug report. Yes Search 5
clang-analyzer For bugs discovered using the Clang analyzer (or scan-build) tools. Yes Search 39
classic For bugs which happen only with the SeaMonkey Classic theme. Yes Search 457
clownshoes This is why we can't have nice things. Yes Search 9
common-issue+ For issues that are commonly seen in support and we will decide if more QA is needed or documentation is needed or if the developers should be alerted. Yes Search 64
common-issue- For issues that we aren't seeing frequently in our regular support channels. Yes Search 27
common-issue? This is used for bugs that are frequently duped on bugzilla to get the support team attention or for things coming down the pipeline. Yes Search 15
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. Yes Search 509
conversion Use this keyword to identify bugs which prevent you from successfully converting your friends and family to using Mozilla Firefox. Yes Search 68
correctness A bug where we don't get the correct numerical/graphical/etc results (may or may not be regression). Yes Search 87
coverity For bugs discovered using the Coverity tools. Yes Search 1240
crash A Critical Severity bug which causes a crash. Yes Search 46685
crashreportid This keyword is added to bugs that have a crash report ID (Talkback or Socorro) reported and which need that stack trace recovered and added to the bug. Yes Search 395
csectype-bounds client security issues due to incorrect boundary conditions (read or write) Yes Search 348
csectype-disclosure Disclosure of sensitive user data, personal information, etc in a client product. Yes Search 102
csectype-dos Used to tag client Denial of Service bugs. For web server denial of service bugs please use wsec-dos as these tend to be more severe. Yes Search 254
csectype-framepoisoning A crash cause by dereferencing a poisoned (deleted) frame, presumed to be limited to a Denial of Service. Yes Search 31
csectype-intoverflow client security issues due to integer overflow Yes Search 55
csectype-nullptr crashes that are due to a guaranteed null dereference. Note that some crashes near zero have a content-controlled offset and should not be given this keyword. Yes Search 106
csectype-oom A client crash or hang that occurs in Out Of Memory conditions Yes Search 61
csectype-other client security issues that don't fit into other categories Yes Search 47
csectype-priv-escalation client privilege escalation security issues Yes Search 70
csectype-race Client security problem due to a race condition Yes Search 49
csectype-sop violations of the client Same Origin Policy (Universal-XSS bugs, for example). Yes Search 41
csectype-spoof client security issues due to UI Redress attacks, either site-on-site ("clickjacking" and friends) or manipulation of the browser UI to fool users into taking the wrong action. Yes Search 193
csectype-uaf client security issues due to a use-after-free Yes Search 568
csectype-undefined Bugs--or potential bugs--due to undefined compiler behavior. Yes Search 2
csectype-uninitialized client security issues due to use of uninitialized memory Yes Search 87
csectype-wildptr client security issues due to pointer misuse not otherwise covered (see csec-uaf, csec-uninitialized, csec-intoverflow, csec-bounds) Yes Search 43
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. Yes Search 154
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 Yes Search 568
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/ Yes Search 707
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.
Yes Search 466
dataloss For bugs that do not crash, but do cause critical data loss. Yes Search 3229
DBI-cust-Business Data & BI work for Business Development Yes none none
DBI-cust-CloudServices Data & BI work for Cloud Services Yes none none
DBI-cust-EngagementAndMarketing Data & BI work for Engagement and Marketing Yes none none
DBI-cust-Finance Data & BI work for Finance Yes none none
DBI-cust-Firefox Data & BI work for Firefox Yes Search 1
DBI-cust-FirefoxOS Data & BI work for FirefoxOS Yes Search 1
DBI-cust-Foundation Data & BI work for Foundation Yes none none
DBI-cust-InsightsAndStrategy Data & BI work for Insights and Strategy Yes none none
DBI-cust-IT Data & BI work for IT Yes Search 1
DBI-cust-Labs Data & BI work for Labs Yes none none
DBI-cust-Marketplace Data & BI work for Marketplace Yes none none
DBI-cust-People Data & BI work for People Yes none none
DBI-cust-Platform Data & BI work for Platform Yes none none
DBI-cust-SUMO Data & BI work for SUMO Yes none none
dev-doc-complete Developer documentation has been created for this bug. Yes Search 3407
dev-doc-needed Developer documentation is required for the changes in this bug. Yes Search 2309
DevAdvocacy Bugs and enhancement requests based on Web developer feedback. Yes Search 243
devrel-needed Bug requires Developer Relations to prioritize and evangelize new features to third party developers. Yes Search 7
devtools-reload Developer used the DevTools Reload system when developing the fix for this bug Yes Search 3
doc-bug-filed Once a documentation bug has been filed to request documentation for a developer-facing change, change the original bug to have this keyword and block the documentation bug. Yes Search 44
dogfood The keyword is used to mark a bug which prevents use of the product by Mozilla developers (breaks bugzilla, for example, or crashes on reading bugmail). If you are not a Mozilla developer, you should not set this keyword. If you don't know whether or not you're a Mozilla developer, you should not set this keyword. Yes Search 743
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. Yes Search 225
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/ Yes Search 132
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/
Yes Search 161
dpi Problems occur at higher or unconventional DPI. Yes Search 1
drupal-admin-fixable For Drupal-powered websites where fixes can be made with the web administrative UI instead of via code fixes to SVN. Yes Search 17
drupal-module Module-related problem with a Drupal-powered website Yes Search 31
drupal-theme Theme-related problem with a Drupal-powered website Yes Search 12
drupal-upgrade Bugs relating to the upgrade of a Drupal module or theme Yes Search 4
dupeme This is likely a duplicate bugreport, but we have too many bugs for us to quickly find the original. Please help keep bugzilla sane by reuniting this bug with its previously-filed original! Yes Search 3
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. Yes Search 223
embed For bugs which are blockers for embedding developmental work. Yes Search 498
event-discussion-needs-final-approval Discussions about Mozilla participation in an event that need final approval. Yes none none
event-discussion-needs-review Discussions about Mozilla participation in an event that are ready to begin. Yes Search 78
event-discussion-no-further-action Discussions about Mozilla participation in an event that require no further action. Yes Search 1
event-discussion-pending-additional-information Discussions about Mozilla participation in an event that need further information. Yes none none
event-discussion-pending-fulfilment Discussions about Mozilla participation in an event that still needs fulfillment. Yes none none
event-discussion-pre-approved-needs-final-approval Discussions about Mozilla participation in an event that are preliminarily approved, but that need final approval. Yes Search 1
event-request-no-further-action Requests for Mozilla to participate in an event that require no further action. Yes none none
event-request-pending-fulfilment Requests for Mozilla to participate in an event that are pending fulfillment. Yes none none
event-request-under-review Requests for Mozilla to participate in an event that are under review. Yes Search 285
example-needed Bug requires a simple, concise code example to demonstrate new feature usage (see guidelines). Yes Search 1
feature Used to flag feature work, major code changes, and any web compatibility/addon/plugin changes to populate https://wiki.mozilla.org/Features/Release_Tracking Yes Search 2362
fixed-aviary1.0 use this keyword to flag a bug as having been fixed on the Aviary 1.0 branch. No Search 1227
fixed-aviary1.0.1 this bug has been fixed for the firefox and thunderbird 1.0.1 release. No Search 82
fixed-aviary1.0.2 This bug was fixed for the aviary 1.0.2 releases No Search 14
fixed-aviary1.0.3 fixed for 1.0.3 No Search 32
fixed-aviary1.0.4 for tagging bugs fixed for Firefox or Thunderbird 1.0.4 No Search 14
fixed-aviary1.0.5 for bugs fixed on the aviary branch for 1.0.5 No Search 65
fixed-aviary1.0.6 for bugs fixed on the aviary branch for 1.0.6 No Search 4
fixed-aviary1.0.7 for bugs fixed in 1.0.7 No Search 19
fixed-aviary1.0.8 for bugs fixed in fixed-aviary1.0.8 No Search 19
fixed-aviary1.0.9 for bugs fixed in aviary1.0.9 No none none
fixed-seamonkey1.0 For bugs fixed in the 1.0 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 58
fixed-seamonkey1.0.1 For bugs fixed in the 1.0.1 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 9
fixed-seamonkey1.0.10 For bugs fixed in the 1.0.10 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No none none
fixed-seamonkey1.0.2 For bugs fixed in the 1.0.2 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 4
fixed-seamonkey1.0.3 For bugs fixed in the 1.0.3 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH No Search 2
fixed-seamonkey1.0.5 For bugs fixed in the 1.0.5 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 1
fixed-seamonkey1.0.6 For bugs fixed in the 1.0.6 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 2
fixed-seamonkey1.0.7 For bugs fixed in the 1.0.7 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 2
fixed-seamonkey1.0.8 For bugs fixed in the 1.0.8 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 4
fixed-seamonkey1.0.9 For bugs fixed in the 1.0.9 release of SeaMonkey off the MOZILLA_1_8_0_BRANCH. No Search 3
fixed-seamonkey1.1 For bugs fixed in the 1.1 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 51
fixed-seamonkey1.1.1 For bugs fixed in the 1.1.1 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 29
fixed-seamonkey1.1.10 For bugs fixed in the 1.1.10 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 6
fixed-seamonkey1.1.11 For bugs fixed in the 1.1.11 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 1
fixed-seamonkey1.1.12 For bugs fixed in the 1.1.12 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No none none
fixed-seamonkey1.1.13 For bugs fixed in the 1.1.13 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 2
fixed-seamonkey1.1.14 For bugs fixed in the 1.1.14 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 1
fixed-seamonkey1.1.15 For bugs fixed in the 1.1.15 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 3
fixed-seamonkey1.1.16 For bugs fixed in the 1.1.16 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 5
fixed-seamonkey1.1.17 For bugs fixed in the 1.1.17 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 3
fixed-seamonkey1.1.18 For bugs fixed in the 1.1.18 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 1
fixed-seamonkey1.1.19 For bugs fixed in the 1.1.19 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 2
fixed-seamonkey1.1.2 For bugs fixed in the 1.1.2 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 15
fixed-seamonkey1.1.3 For bugs fixed in the 1.1.3 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 6
fixed-seamonkey1.1.4 For bugs fixed in the 1.1.4 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 1
fixed-seamonkey1.1.5 For bugs fixed in the 1.1.5 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 6
fixed-seamonkey1.1.6 For bugs fixed in the 1.1.6 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No none none
fixed-seamonkey1.1.7 For bugs fixed in the 1.1.7 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 8
fixed-seamonkey1.1.8 For bugs fixed in the 1.1.8 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 13
fixed-seamonkey1.1.9 For bugs fixed in the 1.1.9 release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 2
fixed-seamonkey1.1a For bugs fixed in the 1.1a release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 175
fixed-seamonkey1.1b For bugs fixed in the 1.1b release of SeaMonkey off the MOZILLA_1_8_BRANCH. No Search 66
fixed-seamonkey2.0 For bugs fixed in the 2.0 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 178
fixed-seamonkey2.0.1 For bugs fixed in the 2.0.1 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 67
fixed-seamonkey2.0.10 For bugs fixed in the 2.0.10 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 1
fixed-seamonkey2.0.11 For bugs fixed in the 2.0.11 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 5
fixed-seamonkey2.0.12 For bugs fixed in the 2.0.12 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 6
fixed-seamonkey2.0.13 For bugs fixed in the 2.0.13 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 2
fixed-seamonkey2.0.14 For bugs fixed in the 2.0.14 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 5
fixed-seamonkey2.0.15 For bugs fixed in the 2.0.15 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No none none
fixed-seamonkey2.0.2 For bugs fixed in the 2.0.2 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 2
fixed-seamonkey2.0.3 For bugs fixed in the 2.0.3 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 68
fixed-seamonkey2.0.4 For bugs fixed in the 2.0.4 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 41
fixed-seamonkey2.0.5 For bugs fixed in the 2.0.5 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 13
fixed-seamonkey2.0.6 For bugs fixed in the 2.0.6 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 13
fixed-seamonkey2.0.7 For bugs fixed in the 2.0.7 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 5
fixed-seamonkey2.0.8 For bugs fixed in the 2.0.8 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 3
fixed-seamonkey2.0.9 For bugs fixed in the 2.0.9 release of SeaMonkey off the MOZILLA_1_9_BRANCH. No Search 5
fixed1.4 Use this keyword when you check in a fix to the 1.4 branch for the 1.4 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4' keyword. No Search 55
fixed1.4.1 Use this keyword when you check in a fix to the 1.4 branch for the 1.4.1 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4' keyword. No Search 96
fixed1.4.2 Use this keyword when you check in a fix to the 1.4 branch for the 1.4.2 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4.2' keyword. No Search 72
fixed1.4.3 Use this keyword when you check in a fix to the 1.4 branch for the 1.4.3 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4.3' keyword. No Search 29
fixed1.4.4 Use this keyword when you check in a fix to the 1.4 branch for the 1.4.4 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4.4' keyword. No Search 12
fixed1.4.5 Use this keyword when you check in a fix to the 1.4 branch for the 1.4.5 release. QA will do branch verification of bugs with this keyword by testing the 1.4 branch and adding the 'verified1.4.5' keyword. No Search 6
fixed1.5 Use this keyword when you check in a fix to the 1.5 branch for the 1.5 release. QA will do branch verification of bugs with this keyword by testing the 1.5 branch and adding the 'verified1.5' keyword. No Search 53
fixed1.6 Use this keyword when you check in a fix to the 1.6 branch for the 1.6 release. QA will do branch verification of bugs with this keyword by testing the 1.6 branch and adding the 'verified1.6' keyword. No Search 21
fixed1.7 This keyword is used to flag a bug as having been fixed for the 1.7 release. No Search 249
fixed1.7.10 for bugs fixed in 1.7.10 No Search 4
fixed1.7.11 for bugs fixed in 1.7.11 No Search 3
fixed1.7.12 for bugs fixed in 1.7.12 No Search 19
fixed1.7.13 for bugs fixed in 1.7.13 No Search 43
fixed1.7.14 for bugs fixed in 1.7.14 No none none
fixed1.7.2 This keyword is used to note that the bug has been fixed on the mini branch for 1.7.2. No Search 5
fixed1.7.3 This keyword is used to note that the bug has been fixed on the mini branch for 1.7.3. No Search 8
fixed1.7.5 This keyword is used to flag a bug as having been fixed for the 1.7 branch for 1.7.5. No Search 286
fixed1.7.6 This keyword is used to flag a bug as having been fixed for the 1.7 branch for 1.7.6. No Search 93
fixed1.7.7 This keyword is used to flag a bug as having been fixed for the 1.7 branch for 1.7.7. No Search 25
fixed1.7.8 for tagging bugs that have been fixed for 1.7.8 No Search 12
fixed1.7.9 for bugs fixed in 1.7.9 No Search 54
fixed1.8 This keyword is used to flag a bug as having been fixed for the 1.8 release. No Search 1246
fixed1.8.0.1 for resolving bugs as fixed for the 1.8.0.1 release No Search 97
fixed1.8.0.10 for resolving bugs as fixed for the 1.8.0.10 release No Search 53
fixed1.8.0.11 for resolving bugs as fixed for the 1.8.0.11 release No Search 1
fixed1.8.0.12 for resolving bugs as fixed for the 1.8.0.12 release No Search 112
fixed1.8.0.13 for resolving bugs as fixed for the 1.8.0.13 release No Search 52
fixed1.8.0.14 for resolving bugs as fixed for the 1.8.0.14 No Search 19
fixed1.8.0.15 for resolving bugs as fixed for the 1.8.0.15 release No Search 71
fixed1.8.0.2 for resolving bugs as fixed for the 1.8.0.2 release No Search 162
fixed1.8.0.3 for resolving bugs as fixed for the 1.8.0.3 release No Search 2
fixed1.8.0.4 for resolving bugs as fixed for the 1.8.0.4 release No Search 168
fixed1.8.0.5 for resolving bugs as fixed for the 1.8.0.5 release No Search 111
fixed1.8.0.6 for resolving bugs as fixed for the 1.8.0.6 release No none none
fixed1.8.0.7 for resolving bugs as fixed for the 1.8.0.7 release No Search 68
fixed1.8.0.8 for resolving bugs as fixed for the 1.8.0.8 release No Search 74
fixed1.8.0.9 for resolving bugs as fixed for the 1.8.0.9 release No Search 43
fixed1.8.1 This keyword is used to flag a bug as having been fixed for the 1.8.1 release. No Search 3511
fixed1.8.1.1 This keyword is used to flag a bug as having been fixed for the 1.8.1.1 release. No Search 358
fixed1.8.1.10 This keyword is used to flag a bug as having been fixed for the 1.8.1.10 release. No Search 50
fixed1.8.1.11 This keyword is used to flag a bug as having been fixed for the 1.8.1.11 release. No Search 1
fixed1.8.1.12 This keyword is used to flag a bug as having been fixed for the 1.8.1.12 release. No Search 174
fixed1.8.1.13 This keyword is used to flag a bug as having been fixed for the 1.8.1.13 release. No Search 82
fixed1.8.1.14 This keyword marks a bug as resolved FIXED for the 1.8.1.14 release. No Search 5
fixed1.8.1.15 This keyword marks a bug as resolved FIXED for the 1.8.1.15 release. No Search 64
fixed1.8.1.16 This keyword marks a bug as resolved FIXED for the 1.8.1.16 release. No Search 3
fixed1.8.1.17 This keyword marks a bug as resolved FIXED for the 1.8.1.17 release. No Search 43
fixed1.8.1.18 This keyword marks a bug as resolved FIXED for the 1.8.1.18 release. No Search 20
fixed1.8.1.19 This keyword marks a bug as resolved FIXED for the 1.8.1.19 release. No Search 15
fixed1.8.1.2 This keyword is used to flag a bug as having been fixed for the 1.8.1.2 release. No Search 185
fixed1.8.1.20 This keyword marks a bug as resolved FIXED for the 1.8.1.20 milestone. No none none
fixed1.8.1.21 This keyword marks a bug as resolved FIXED for the 1.8.1.21 milestone. No Search 32
fixed1.8.1.22 This keyword marks a bug as resolved FIXED for the 1.8.1.22 milestone. No Search 33
fixed1.8.1.23 This keyword marks a bug as resolved FIXED for the 1.8.1.23 milestone. No Search 14
fixed1.8.1.24 This keyword marks a bug as resolved FIXED for the 1.8.1.24 milestone. No Search 34
fixed1.8.1.3 This keyword is used to flag a bug as having been fixed for the 1.8.1.3 release. No Search 86
fixed1.8.1.4 This keyword is used to flag a bug as having been fixed for the 1.8.1.4 release. No Search 228
fixed1.8.1.5 This keyword is used to flag a bug as having been fixed for the 1.8.1.5 release. No Search 122
fixed1.8.1.6 This keyword is used to flag a bug as having been fixed for the 1.8.1.6 release. No Search 7
fixed1.8.1.7 This keyword is used to flag a bug as having been fixed for the 1.8.1.7 release. No Search 2
fixed1.8.1.8 This keyword is used to flag a bug as having been fixed for the 1.8.1.8 release. No Search 113
fixed1.8.1.9 This keyword is used to flag a bug as having been fixed for the 1.8.1.9 release. No Search 3
fixed1.9.0 This keyword is used to flag a bug as having been fixed for the 1.9.0 release. This keyword is required to simplify branch-management queries. No Search 2
fixed1.9.0.1 This keyword is used to flag a bug as having been fixed for the 1.9.0.1 release. No Search 44
fixed1.9.0.10 This keyword is used to flag a bug as having been fixed for the 1.9.0.10 release. No none none
fixed1.9.0.11 This keyword is used to flag a bug as having been fixed for the 1.9.0.11 release. No Search 29
fixed1.9.0.12 This keyword is used to flag a bug as having been fixed for the 1.9.0.12 release. No Search 45
fixed1.9.0.13 This keyword is used to flag a bug as having been fixed for the 1.9.0.13 release. No Search 4
fixed1.9.0.14 This keyword is used to flag a bug as having been fixed for the 1.9.0.14 release. No Search 22
fixed1.9.0.15 This keyword is used to flag a bug as having been fixed for the 1.9.0.15 release. No Search 18
fixed1.9.0.16 This keyword is used to flag a bug as having been fixed for the 1.9.0.16 release. No Search 17
fixed1.9.0.17 This keyword is used to flag a bug as having been fixed for the 1.9.0.17 release. No none none
fixed1.9.0.18 This keyword is used to flag a bug as having been fixed for the 1.9.0.18 release. No Search 20
fixed1.9.0.19 This keyword is used to flag a bug as having been fixed for the 1.9.0.19 release. No Search 6
fixed1.9.0.2 This keyword is used to flag a bug as having been fixed for the 1.9.0.2 release. No Search 121
fixed1.9.0.20 This keyword is used to flag a bug as having been fixed for the 1.9.0.20 release. No Search 24
fixed1.9.0.3 This keyword is used to flag a bug as having been fixed for the 1.9.0.3 release. No none none
fixed1.9.0.4 This keyword is used to flag a bug as having been fixed for the 1.9.0.4 release. No Search 53
fixed1.9.0.5 This keyword is used to flag a bug as having been fixed for the 1.9.0.5 release. No Search 45
fixed1.9.0.6 This keyword is used to flag a bug as having been fixed for the 1.9.0.6 release. No Search 20
fixed1.9.0.7 This keyword is used to flag a bug as having been fixed for the 1.9.0.7 release. No Search 20
fixed1.9.0.8 This keyword is used to flag a bug as having been fixed for the 1.9.0.8 release. No none none
fixed1.9.0.9 This keyword is used to flag a bug as having been fixed for the 1.9.0.9 release. No Search 14
fixed1.9.1 This keyword is used to flag a bug as having been fixed for the 1.9.1 release. No Search 1818
fixed1.9.1.1 This keyword is used to flag a bug as having been fixed for the 1.9.1.1 release. No Search 5
fixedOEM Use this keyword when you check in a fix to the oem branch (to be named later). QA will verify bugs with this keyword by replacing it with 'verifiedOEM' keyword. Yes Search 63
flashplayer For bugs affecting flashplayer Yes Search 373
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. Yes Search 290
footprint A bug that affects memory use, usually through excessive memory allocation or code size. (For leaks, use the "mlk" keyword instead.) Yes Search 1022
foxfood Bugs found through the Firefox OS Foxfooding program (https://mana.mozilla.org/wiki/display/PM/Foxfooding+Program) Yes Search 1404
good-first-bug An entry-level bug that has guidance to help people make their first contribution to Mozilla. Yes Search 104
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 crash report from Talkback or Socorro is generated to help us isolate the bug. Yes Search 5758
helpwanted Bugs or features which require coding assistance to fix or implement. Yes Search 4530
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". Yes Search 38
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 Yes Search 229
html5 Bugs that affect compliance with W3C HTML5. Yes Search 544
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. Yes Search 124
imap-interop Interoperability bugs with various IMAP mail servers Yes Search 208
in-triage Bugs that are actively being triaged but not yet ready for an engineering decision. Yes Search 655
infra-failure Indicates a failure in the environment, for example hardware failure, dropped internet etc. Yes Search 1
inputmethod Bugs that are related to IM (Input Method) which is complex text inputting system. IM is also known as IME (Input Method Editor), FEP (Front End Processor) or TIP (Text Input Processor). The bugs can be in any modules, e.g., widget, content, editor, layout and toolkit. Yes Search 842
intermittent-failure For the tracking of intermittent test failures for tests that report to Treeherder (used for bug suggestions). If you use this keyword for things other than this, there is a large chance your bug will get mass-closed at some point. Yes Search 24082
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. Yes Search 4133
jp-critical Bugs that are deemed critical to Japanese users. Yes Search 155
js1.5 JavaScript 1.5 blocking bugs. Yes Search 533
js1.6 JavaScript 1.6 blocking bugs. Yes Search 54
js1.7 JavaScript 1.7 blocking bugs. Yes Search 19
jsbugmon Indicates the bug was created by the JavaScript fuzzers and is used by the fuzzers to track those bugs. Yes Search 27
klocwork For bugs discovered using the Klocwork tools. Yes Search 42
l12y Use this keyword for any bug related to localizability issues like hardcoded strings, sizing information, hardcoded fonts... Yes Search 1851
late-l10n This keyword is to be added to bugs which have patches that landed after the localization freeze (typically "after beta") and which impact localizable strings. Localizers can query bugzilla for bugs with this keyword and the approval1.x+ flag to find l10n-impact changes that happened after the 1.x l10n freeze. Yes Search 786
leave-open Instructs merge tools to leave the bug open when the patches are merged to mozilla-central. Yes Search 868
losing-users Use this keyword when there is some evidence that we are actually losing users as a result of an issue or bug, (perhaps crash or social media comments for example). Yes Search 5
mail-integration Used for Calendar bugs that would have benefit for Thunderbird (i.e., adding ids, great features that would improve user experience) Yes Search 27
main-thread-io Use this keyword to mark bugs related to performing synchronous I/O (such as to disk files or databases) on the main thread. These bugs harm the responsiveness of applications. Yes Search 171
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. Yes Search 4352
mlk A memory leak bug: memory is never released or is released only during shutdown. The bug report should include information that indicates which objects leak, such as a log from one of Mozilla's leak-detection tools. Yes Search 3884
mobile For bugs which are important to mobile developmental work. Yes Search 701
moc:triage Bugs that are actively being triaged for references (mostly new hires and jr. team members) Yes Search 21
modern For bugs which occur with only the Modern theme included in Mozilla builds. Yes Search 299
multi-monitors Problems occur for multiple monitors. Yes Search 5
multiprocess bugs associated with multiple content processes Yes none none
needURLs The Crash Stats team needs sample URLs for this crash bug. Yes none none
nightly-community Bug reported by a member of the Firefox Nightly community. Used to triage community-reported bugs and measure the impact of our core community on product quality. Yes Search 75
otoro Use this keyword when designating bugs found during testing of the B2G Otoro device. Yes Search 19
p2v Used by IT to mark bugs which involve converting servers that are physical machines to virtual machines. Yes Search 133
papercut An issue that can affect hurt daily use of Firefox OS. This annoyance could be user or developer-facing or falls into any of the categories related to feature/functional enhancement, defect or poor performance. Yes Search 65
perf A bug that affects speed or responsiveness. (For memory use issues, use "footprint" or "mlk" instead.) Yes Search 12770
platform For marking bugs that affect our Mozilla-as-platform story. Yes Search 40
polish Bugs which require only a small change for a noticable improvement in the user interface Yes Search 5613
power Use this keyword for anything related to measuring or reducing the power usage of our applications. Yes Search 118
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. Yes Search 2255
privacy Bugs relating to user privacy which do not belong in the Security: General component. Yes Search 1118
privacy-review-needed The changes in this bug require a privacy review. Yes Search 86
productization For localizations and Mozilla business development initiatives that require external verification and team consensus regarding the inclusion of third party services in Mozilla software. Productization services include search providers in the browser, links to third parties hosted on Mozilla web properties, third party protocol handlers (mailto:, webcal:, irc:, etc.), RSS feeds, and any other items further describing localization and business development of Mozilla software. Yes Search 703
productwanted Information needed from Product team. Yes Search 277
push-needed For website/webtool (but usually just AMO) bugs that have been checked in but not yet pushed to production servers. Yes Search 100
qablocker Use this keyword for bugs that are blocking testing (manual or automated testing of an area) and need to be fixed by the next Beta or RC milestone. Yes Search 179
qaurgent Use this keyword to request direct involvement by the QA team, use in conjunction with one of the other keywords to designate the exact nature of the request Yes Search 15
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. Note what QA work is wanted in the whiteboard. Please remove this keyword when the wanted QA work has been completed. Yes Search 3588
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 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. Yes Search 55179
regressionwindow-wanted This bug is a regression, and would strongly benefit from someone narrowing down the time period where it happened, ideally to a specific checkin. Yes Search 368
relnote This bug need to be put on release notes for next milestone announcement. No Search 1258
reproducible This keyword is used to flag a bug when it includes a set of steps to reliably reproduce the bug. Yes Search 3104
rtl A bug tied to or exposed by languages with a right-to-left (RTL) writing system. Yes Search 970
sec-audit Bug requires a code audit to investigate potential security problems. Yes none none
sec-critical Exploitable vulnerabilities which can lead to the widespread compromise of many users. Yes none none
sec-high Obtain confidential data from other sites the user is visiting or the local machine, or inject data or code into those sites, requiring no more than normal browsing actions. Exploitable web vulnerabilities that can lead to the targeted compromise of a small number of users. Yes none none
sec-incident Issues resulting in an incident response or 'chemspill' actions by the security team. Yes none none
sec-low Minor security vulnerabilities such as leaks or spoofs of non-sensitive information. Missing best practice security controls. Yes none none
sec-moderate Vulnerabilities which can provide an attacker additional information or positioning that could be used in combination with other vulnerabilities. Yes none none
sec-other Bugs that may not be exploitable security issues but are kept confidential to protect sensitive information. Yes none none
sec-vector Flaws not in Mozilla-controlled software but that can cause security problems for Mozilla users. For example: system libraries, 3rd-party plugins. Yes none none
sec-want New features or improvement ideas related to security Yes none none
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. Yes Search 657
selenium A Selenium test has been created to reproduce/test this Yes Search 66
sheriffing-P1 Bugs that affect the sheriffing of Gecko/Firefox trees. Yes Search 135
sheriffing-P2 Bugs that affect the sheriffing of Gecko/Firefox trees. Yes Search 32
sheriffing-P3 Bugs that affect the sheriffing of Gecko/Firefox trees. Yes Search 12
sheriffing-untriaged Bugs that affect the sheriffing of Gecko/Firefox trees. Yes Search 48
shockwave For bugs specific to incompatibilities with mozilla products and the MacroMedia Shockwave plug-in. Yes Search 90
singleprocess bugs associated with a single content process Yes none none
site-compat Used to indicate bugs which may affect backward compatibility of Web sites or Web applications. Yes Search 689
smoketest Means that this bug prevents the smoketests from passing. Yes Search 2068
spring-cleaning Used to denote IT bugs that are targeted for the spring cleaning project. Yes Search 506
stackwanted For crashing bugs which need stacktrace information to be added to description field to help out engineers debug the problem. Yes Search 2560
steps-wanted A bug which would greatly benefit from someone identifying steps to reproduce. Yes Search 436
student-project Bugs and enhancement requests that would be appropriate for students looking to work on a Mozilla project as part of a course. These should have someone or a group willing to mentor, offer help, and do reviews. See guidelines on using this keyword. Yes Search 229
talos-regression Bugs filed based on a regression detected by the Talos performance testing suite. Yes Search 37
technote For technotes at devmo Yes Search 1
testcase Indicates that a simplified test case is done and included in bug report. Yes Search 28897
testcase-wanted This bug would strongly benefit from a testcase or from additional testcases in order to be fixed. This keyword may indicate that any existing testcases are too complex and need to be reduced to much simpler tests in order to find or debug the source of the problem. Check the comments of the bug to discover exactly what is wanted. Yes Search 470
testtracker Use this keyword to flag a bug which contains information that should become a test added to the test tracker tool. The tool currently hosts application smoketest and Firefox functional test. Yes Search 5
thirdparty Keyword used for flagging any third party issues and identifying the issues for a particular release. Yes Search 16
top100 Bug with a top 100 site based on Alexa top 100 Yes Search 753
top50 Please use this keyword to flag any bugs for websites identified in the top 50 of Firefox's "Report a Broken Web Site" list. Yes Search 34
top500 bugs with top 500 sites based on Alexa top 500. Yes Search 230
topcrash Bugs created from highly visible crashes per the crash report data. Yes Search 3080
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. Yes Search 297
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. Yes Search 93
topcrash-android-armv6 Bugs created from highly visible Android ARMv6 crashes per the crash report data. No Search 1
topcrash-android-armv7 Bugs created from highly visible Android ARMv7 crashes per the crash report data. Yes Search 92
topcrash-android-x86 Bugs created from highly visible Android x86 crashes per the crash report data. Bugs created from highly visible Android x86 crashes per the crash report data. Yes Search 4
topcrash-b2g Bugs created from highly visible B2G crashes per the crash report data. Yes Search 22
topcrash-linux Bugs created from highly visible Linux crashes per the crash report data. Yes Search 10
topcrash-mac Bugs created from highly visible Mac OS X crashes per the crash report data. Yes Search 57
topcrash-metro Bugs created from highly visible Metro crashes per the crash report data. Yes Search 8
topcrash-plugin Bugs created from highly visible plugin crashes per the crash report data. Yes Search 7
topcrash-thunderbird Bugs created from highly visible Thunderbird crashes per the crash report data. Yes Search 90
topcrash-win Bugs created from highly visible Windows crashes per the crash report data. Yes Search 256
topembed Use this keyword for bugs which are critical to embedding. Yes Search 528
topembed+ The Netscape embedding evaluation team will add this keyword to bugs which have been accepted for the next Netscape embedding release. Yes Search 714
topembed- This keyword will be added to bugs which the Netscape embedding evaluation team has rejected for the next Netscape embedding release. Yes Search 317
topmlk A high-profile memory leak bug. (These bugs should also have the "mlk" keyword.) Yes Search 17
topperf A high-profile speed or responsiveness issue. (These bugs should also have the "perf" keyword.) Yes Search 97
treeherder Bugs affecting Treeherder that are outside of the Treeherder components. Yes Search 38
trychooser For bugs related to Release Engineering's TryChooser, which lets you select specific jobs you want to run on tryserver. Covers both the parsing of trychooser syntax as well as the syntax generator here. Yes Search 136
ue For bugs with a specific detailed suggestion for improvement of the user experience. The problem describes a confusing or unhelpful aspect of the user interface. Yes Search 478
uiwanted For bugs that require UI design support, either for a requested feature enhancement, some new function which needs some UI, or a fix to existing UI. Yes Search 1814
unagi Use this keyword when designating bugs found during testing of the B2G Unagi device. Yes Search 885
urwanted User research input needed. Yes Search 5
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." Yes Search 247
user-doc-complete User documentation has been created for this bug. Yes Search 60
user-doc-needed User documentation is required for the changes in this bug. Yes Search 176
ux-affordance User experience principle: controls should visually express how the user should interact with them. Yes Search 23
ux-consistency User experience principle: in general software should be internally consistent with itself, and externally consistent with similar interfaces to leverage the user's existing knowledge. Yes Search 421
ux-control User experience principle: users should always feel like they are in control of their software. (This principle is often the nemesis of ux-interruption, especially in cases where developers assume users want more control than they actually want). Yes Search 166
ux-discovery User experience principle: users should be able to discover functionality and information by visually exploring the interface, they should not be forced to recall information from memory. (This is often the nemesis of ux-minimalism since additional visible items diminish the relative visibility of other items being displayed). Yes Search 122
ux-efficiency User experience principle: interfaces should be as efficient as possible, minimizing the complexity of actions and the overall time to complete a task. Yes Search 202
ux-error-prevention User experience principle: interfaces should proactively try to prevent errors from happening. Yes Search 150
ux-error-recovery User experience principle: interfaces should proactively help users recover from both user errors and technology errors. (A preferable case is to address through ux-error-prevention so that the error does not occur). Yes Search 45
ux-implementation-level User experience principle: interfaces should not be organized around the underlying implementation and technology in ways that are illogical, or require the user to have access to additional information that is not found in the interface itself. Yes Search 58
ux-interruption User experience principle: interfaces should not interrupt the user. Interfaces should never ask the user a question that they are not prepared to answer simply for a false sense of ux-control. In general software should only speak when spoken to. Yes Search 49
ux-jargon User experience principle: users should not be required to understand any form of implementation level terminology. (This principle is a special case of ux-implementation-level). Yes Search 39
ux-minimalism User experience principle: interfaces should be as simple as possible, both visually and interactively. Interfaces should avoid redundancy. (This principle is often the nemesis of ux-discovery since removing or hiding items deep into the interface forces the user to rely more on memory than recognition). Yes Search 73
ux-mode-error User experience principle: users should not encounter errors because the interface is in a different state than they expected it to be. (This principle is a special case of ux-error-prevention). Yes Search 56
ux-natural-mapping User experience principle: controls should be placed in the correct location relative to the effect that they will have. Yes Search 28
ux-tone User experience principle: interfaces should not blame the user, or communicate in a way that is overly negative or dramatic. Yes Search 20
ux-trust Use keyword to tag bugs that have an impact on user trust of our products, but aren't necessarily or strictly issues due to performance. For example, if I have to tap a text field 5 times to get it to register and bring up the keyboard, as a user, I will come to expect that and not trust that I can select the text field consistently. This could be due to a small touch target, and is not a performance issue. Yes Search 46
ux-undo User experience principle: actions should support undo so that users remain in control. (This principle is a special case of ux-control). Yes Search 17
ux-userfeedback User experience principle: interfaces should provide feedback about their current status. Users should never wonder what state the system is in. Yes Search 215
ux-visual-hierarchy User experience principle: controls that are more important or more commonly used should leverage visual variables such as size and contrast so that they have more dominance and weight relative to other controls. (This principle is an adaption of ux-discovery). Yes Search 31
valgrind For bugs discovered using the valgrind tool. Yes Search 433
verified-aurora This keyword is used to flag a bug as having been verified for the aurora release. Yes Search 180
verified-beta This keyword is used to flag a bug as having been verified for the beta release. Yes Search 234
verified-production For website/webtool bugs that have been verified on the production servers. Yes Search 61
verified1.7 Use this keyword to indicate that a fix has been verified on the 1.7 branch for the 1.7 release. No Search 94
verified1.7.13 verified 1.7.13 bugs No Search 67
verified1.7.6 Use this keyword to indicate that a fix has been verified on the 1.7 branch for the 1.7.6 release. No Search 12
verified1.7.7 Use this keyword to indicate that a fix has been verified on the 1.7 branch for the 1.7.7 release. No none none
verified1.8 Use this keyword to indicate that a fix has been verified on the 1.8 branch for the 1.8 release. No Search 251
verified1.8.0.1 for verifying that bugs are fixed for the 1.8.0.1 release No Search 76
verified1.8.0.10 for verifying that bugs are fixed for the 1.8.0.10 release No Search 78
verified1.8.0.11 for verifying that bugs are fixed for the 1.8.0.11 release No Search 4
verified1.8.0.12 for verifying that bugs are fixed for the 1.8.0.12 release No Search 67
verified1.8.0.13 for verifying that bugs are fixed for the 1.8.0.13 release No Search 39
verified1.8.0.14 for verifying that bugs are fixed for the 1.8.0.14 release No Search 13
verified1.8.0.15 for verifying that bugs are fixed for the 1.8.0.15 release No none none
verified1.8.0.2 for verifying that bugs are fixed for the 1.8.0.2 release No Search 127
verified1.8.0.3 for verifying that bugs are fixed for the 1.8.0.3 release No Search 2
verified1.8.0.4 for verifying that bugs are fixed for the 1.8.0.4 release No Search 85
verified1.8.0.5 for verifying that bugs are fixed for the 1.8.0.5 release No Search 90
verified1.8.0.6 for verifying that bugs are fixed for the 1.8.0.6 release No Search 1
verified1.8.0.7 for verifying that bugs are fixed for the 1.8.0.7 release No Search 88
verified1.8.0.8 for verifying that bugs are fixed for the 1.8.0.8 release No Search 37
verified1.8.0.9 for verifying that bugs are fixed for the 1.8.0.9 release No Search 80
verified1.8.1 This keyword is used to flag a bug as having been verified for the 1.8.1 release. No Search 716
verified1.8.1.1 This keyword is used to flag a bug as having been verified for the 1.8.1.1 release. No Search 214
verified1.8.1.10 This keyword is used to flag a bug as having been verified for the 1.8.1.10 release No Search 31
verified1.8.1.11 This keyword is used to flag a bug as having been verified for the 1.8.1.11 release No Search 1
verified1.8.1.12 This keyword is used to flag a bug as having been verified for the 1.8.1.12 release No Search 119
verified1.8.1.13 This keyword is used to flag a bug as having been verified for the 1.8.1.13 release No Search 60
verified1.8.1.14 This keyword is used to flag a bug as having been verified for the 1.8.1.14 release No Search 2
verified1.8.1.15 This keyword is used to flag a bug as having been verified for the 1.8.1.15 release No Search 52
verified1.8.1.16 This keyword is used to flag a bug as having been verified for the 1.8.1.16 release No Search 7
verified1.8.1.17 This keyword is used to flag a bug as having been verified for the 1.8.1.17 release No Search 40
verified1.8.1.18 This keyword is used to flag a bug as having been verified for the 1.8.1.18 release No Search 28
verified1.8.1.19 This keyword is used to flag a bug as having been verified for the 1.8.1.19 release No Search 22
verified1.8.1.2 This keyword is used to flag a bug as having been verified for the 1.8.1.2 release. No Search 199
verified1.8.1.20 This keyword is used to flag a bug as having been verified for the 1.8.1.20 milestone No Search 3
verified1.8.1.21 This keyword is used to flag a bug as having been verified for the 1.8.1.21 milestone No Search 3
verified1.8.1.22 This keyword is used to flag a bug as having been verified for the 1.8.1.22 milestone No Search 17
verified1.8.1.23 This keyword is used to flag a bug as having been verified for the 1.8.1.23 milestone No Search 1
verified1.8.1.24 This keyword is used to flag a bug as having been verified for the 1.8.1.24 milestone No Search 10
verified1.8.1.3 This keyword is used to flag a bug as having been verified for the 1.8.1.3 release. No Search 192
verified1.8.1.4 This keyword is used to flag a bug as having been verified for the 1.8.1.4 release. No Search 177
verified1.8.1.5 This keyword is used to flag a bug as having been verified for the 1.8.1.5 release. No Search 87
verified1.8.1.6 This keyword is used to flag a bug as having been verified for the 1.8.1.6 release No Search 3
verified1.8.1.7 This keyword is used to flag a bug as having been verified for the 1.8.1.7 release No Search 1
verified1.8.1.8 This keyword is used to flag a bug as having been verified for the 1.8.1.8 release No Search 125
verified1.8.1.9 This keyword is used to flag a bug as having been verified for the 1.8.1.9 release No Search 8
verified1.9.0 This keyword is required to simplify branch-management queries. No none none
verified1.9.0.1 This keyword is used to flag a bug as having been verified for the 1.9.0.1 release. No Search 59
verified1.9.0.10 This keyword is used to flag a bug as having been verified for the 1.9.0.10 release. No Search 4
verified1.9.0.11 This keyword is used to flag a bug as having been verified for the 1.9.0.11 release. No Search 48
verified1.9.0.12 This keyword is used to flag a bug as having been verified for the 1.9.0.12 release. No Search 43
verified1.9.0.13 This keyword is used to flag a bug as having been verified for the 1.9.0.13 release. No Search 8
verified1.9.0.14 This keyword is used to flag a bug as having been verified for the 1.9.0.14 release. No Search 30
verified1.9.0.15 This keyword is used to flag a bug as having been verified for the 1.9.0.15 release. No Search 29
verified1.9.0.16 This keyword is used to flag a bug as having been verified for the 1.9.0.16 release. No Search 22
verified1.9.0.17 This keyword is used to flag a bug as having been verified for the 1.9.0.17 release. No Search 2
verified1.9.0.18 This keyword is used to flag a bug as having been verified for the 1.9.0.18 release. No Search 10
verified1.9.0.19 This keyword is used to flag a bug as having been verified for the 1.9.0.19 release. No Search 16
verified1.9.0.2 This keyword is used to flag a bug as having been verified for the 1.9.0.2 release. No Search 106
verified1.9.0.20 This keyword is used to flag a bug as having been verified for the 1.9.0.20 release. No none none
verified1.9.0.3 This keyword is used to flag a bug as having been verified for the 1.9.0.3 release. No Search 1
verified1.9.0.4 This keyword is used to flag a bug as having been verified for the 1.9.0.4 release. No Search 86
verified1.9.0.5 This keyword is used to flag a bug as having been verified for the 1.9.0.5 release. No Search 67
verified1.9.0.6 This keyword is used to flag a bug as having been verified for the 1.9.0.6 release. No Search 52
verified1.9.0.7 This keyword is used to flag a bug as having been verified for the 1.9.0.7 release. No Search 34
verified1.9.0.8 This keyword is used to flag a bug as having been verified for the 1.9.0.8 release. No Search 4
verified1.9.0.9 This keyword is used to flag a bug as having been verified for the 1.9.0.9 release. No Search 58
verified1.9.1 This keyword is used to flag a bug as having been verified for the 1.9.1 release. No Search 2026
verified1.9.1.1 This keyword is used to flag a bug as having been verified for the 1.9.1.1 release. No Search 24
verified1.9.2 This keyword is used to flag a bug as having been verified for the 1.9.2 release. No Search 610
verified1.9.3 This keyword is used to flag a bug as having been verified for the 1.9.3 release. No Search 8
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.
Yes Search 1150
website-graveyard Old, retired Websites. Yes Search 1
wsec-applogic Issue related to application logic Yes none none
wsec-appmisconfig Application software misconfiguration issue Yes none none
wsec-authentication Website or server authentication security issues (lockouts, password policy, etc) Yes none none
wsec-authorization web/server authorization security issues Yes none none
wsec-automation-attack Anti-automation bypass or insufficient anti-automation controls Yes none none
wsec-bruteforce Vulnerable to brute force attack Yes none none
wsec-client Abuse of web browser/client Yes none none
wsec-crossdomain Issue such as x-frame-options, crossdomain.xml, cross site sharing settings Yes none none
wsec-crypto Crypto related items such as password hashing Yes none none
wsec-csrf Cross-Site Request Forgery (CSRF) bugs in server products Yes none none
wsec-deplib Issue related to flaw in library or other dependency Yes none none
wsec-dir-index Directory indexing issue Yes none none
wsec-disclosure Disclosure of sensitive data, personal information, etc from a web service Yes none none
wsec-dos Used to denote web server Denial of Service bugs. For similar bugs in client software please use csec-dos instead. Yes none none
wsec-email Abuse of email functionality Yes none none
wsec-errorhandling Any error handling issue Yes none none
wsec-fileinclusion RFI and LFI issues Yes none none
wsec-headers Missing or misconfigured security-related HTTP headers Yes none none
wsec-http HTTP protocol issues other than security headers Yes none none
wsec-http-header-inject HTTP header injection issue such as CSRF Yes none none
wsec-impersonation Impersonation / Spoofing attacks (UI Redress, etc) Yes none none
wsec-injection Injection attacks other than SQLi, XSS, XML, OS Command Injection, null byte, and buffer overflow. Yes none none
wsec-input Failure to perform input validation. Most often you will probably use the xss tag instead Yes none none
wsec-logging Logging issues such as requests for CEF log points. Yes none none
wsec-nullbyte Null bite injection issue Yes none none
wsec-objref Direct object reference vulnerability Yes none none
wsec-oscmd Operating system command injection Yes none none
wsec-other web/server security issues that don't fit into other categories Yes none none
wsec-overflow Buffer or integer overflow issue Yes none none
wsec-redirect Redirect issues Yes none none
wsec-selfxss XSS where the attacker must trick the user into copying and pasting the XSS string into their own browser. Yes none none
wsec-serialization Serialization and deserialization issues Yes none none
wsec-servermisconfig Server OS or application server misconfiguration issue Yes none none
wsec-session Issues related to sesson management (Session fixation, etc) Yes none none
wsec-sqli SQL Injection Yes none none
wsec-tls TLS/SSL related issue Yes none none
wsec-traversal Directory and other resource traversal issues Yes none none
wsec-weakpasswd Issue related to password strength Yes none none
wsec-xml XML attribute blowup, entity expansion, external entity, and XPATH, and other injection bugs Yes none none
wsec-xss Cross-Site Scripting (XSS) bugs in server products Yes none none
xhtml Bugs related to support for XHTML Yes Search 139