How to report issues properly? READ BEFORE REPORTING ISSUES!

[Aris-t2]

Before posting issues make sure...

• ...everything previously available in chrome folder got backuped and removed
• ...the latest '.zip' release incl. all files and correct folder structure is inside profiles chrome folder
• ...no @namespace references are inside CSS files
• ...this projects code was not mixed with CSS from other/custom/own files

---

1. Hit "new issue" button on this page or hit "issues" and then hit "new issue" button.

• you must be signed into Github to be able to report an issue

2. Add a proper issue title.

• if the issue is related to 'NoiaButtons' code, add [NB] to title

If it only happens...

• ...on a specific OS, also add [Win], [Lin] or [macOS] to the title.
• ...on a specific browser version, also add [Fx 'version number'] to the title, e.g. [Fx57]
• ...on a specific OS theme, also add [OS theme name] to the title, e.g. [Aero Glass], [Classic]
• ...with a specific browser theme, also add [browser theme name] to the title

Ex. 1: [Win][Lin][Fx58] wrong active tab color
Ex. 2: [NB][Fx57] downloads buttons too small

3. Post a screenshot of your full browser window and point to the issue on it.

• Attach screenshot to your post by dragging & dropping it into the post OR
• Post a link to an uploaded screenshot (Imgur, Tinypic, Dropbox etc.)

4. Describe the issue

• what should or should not happen
• what does happen

5. Post your configuration

• OS / OS version / OS theme
• browser (default Firefox or a fork)
• browser version (default, beta, developer/Aurora, Nightly) and version number
• browser theme (default theme, dark/light theme, lw-theme)
• other add-ons (if you find a conflict)