| <code style="color:green;"><Firebug version></code> || Version of Firebug the issue is seen on (e.g. <code style="color:green;">1.11-b3</code>); generally required when triaging an issue

+

|-

+

| <code style="color:green;">extension-issue</code> || An issue related to a Firebug extension; The extension name needs to be provided as another label (e.g. <code style="color:green;">netexport-0.9-b2</code>).

+

|-

+

| <code style="color:green;">contribution</code> || A non-Firebug-member provides a patch for an issue and we apply it

+

|-

+

| <code style="color:green;">platform</code> || Issue needing platform support or a fix on platform side

+

|-

+

| <code style="color:green;">refactoring</code> || Issue related to code refactoring (no bug fix or UI changes); requires the type of the issue to be set to <code>Type-Enhancement</code>

Revision as of 11:02, 6 December 2012

Contents

Coding

Changes, which should be included in a bug fix release first need to be tested in an alpha release.E.g. fixes, which should be included in 1.10.4 need to be released in an alpha version of 1.11 first.

Preferences

Avoid introducing new preferences when they are unnecessary, i.e. try to reuse existing preferences or to find a better UI instead.E.g. Instead of adding a preference for string cropping reuse firebug.extensions.stringCropLength

Give your preference a good name.

Give it a panel and usage independent name if it's a preference that could be reused somewhere elseE.g. extensions.firebug.showUserAgentCSS

Reuse the naming convention of similar preferences.E.g. if you want to specify the max. number of displayed elements, you should append "Limit" to the name as it's done for extensions.firebug.multiHighlightLimit, extensions.firebug.net.logLimit.

Prefix panel/module specific preferences with the panel/module nameE.g. like extensions.firebug.net.hiddenColumnsextensions.firebug.cache.mimeTypes

Localizations

Make sure you allow localization of all string labels you add to the UI.

Give your localization keys a good name.

Give it a panel and usage independent name if it's a localization that could be reused at different places