BMO/Modal UI FAQ: Difference between revisions
(→How can (blank) be changed? Can (blank) be changed?: more my style) |
(→The Classic/Dusk Skin Looks Ugly: better wording) |
||
| Line 29: | Line 29: | ||
[[File:BMO-UserPref-Remember visibility of header sections when viewing a bug.png]] | [[File:BMO-UserPref-Remember visibility of header sections when viewing a bug.png]] | ||
== | == Why does this look so weird using the Dusk or Classic skin? == | ||
We recommend [https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#skin_row switching to the Mozilla Skin]. | We recommend [https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#skin_row switching to the Mozilla Skin]. | ||
Revision as of 22:31, 1 March 2017
How can (blank) be changed? Can (blank) be changed?
Contrary to a popular rumor, BMO is software rather than stoneware and as thus quite malleable. You can reported Report Bugs or Feature Requests, chat with us on IRC, and find our code on github.
If you feel ambitious, we gladly take pull requests and patches as well.
Why Can't I Edit Fields?
In Bug Modal, fields are not editable by default. To edit fields, use the "Edit Bug" button located in the top-right corner of the bug form, as illustrated below.
How do I Collapse/Expanded Fields
Click on the drop-down error under the Edit button.
How do I Collapse/Expanded Fields by Default?
The expanded or collapsed state of each section ("module") is remembered by default. If you wish to change this, you can do so by changing Remember visibility of header sections when viewing a bug on the user preferences page.
Why does this look so weird using the Dusk or Classic skin?
We recommend switching to the Mozilla Skin. We will also accept patches for the Classic or Dusk skins, but working on them is not a priority.
