BMO/Modal UI FAQ: Difference between revisions

← Older edit

BMO/Modal UI FAQ (view source)

Revision as of 19:59, 15 March 2017

818 bytes added , 15 March 2017

→‎How can (blank) be changed? Can (blank) be changed?: Typo ( as vs is )

Bomfog

29

edits

@@ Line 1: / Line 1: @@
 == How can (blank) be changed? Can (blank) be changed? ==
-Luckily BMO is not set in stone! We can respond to bug reports and feature requests
+Contrary to a popular rumor, BMO is software rather than stoneware and is thus quite malleable.
-reported [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=User%20Interface:%20Modal&format=__default__ using BMO].
+You can [https://bugzilla.mozilla.org/enter_bug.cgi?product=bugzilla.mozilla.org&component=User%20Interface:%20Modal&format=__default__ Report Bugs or Feature Requests], chat with us on [ircs://mozilla.org#bmo IRC], and find our code on [https://github.com/mozilla-bteam/bmo github].
-You also reach out on the #bmo IRC channel on irc.mozilla.org.
+If you feel ambitious, we consider pull requests and patches as well.
-The code is on github: [https://github.com/mozilla-bteam/bmo mozilla-bteam/bmo] and we can consider
+== Why is it Experimental? ==
-both patches and pull requests.
-== Why Can't I Edit Fields? ==
+Mostly inertia. There is nothing experimental at this point. It's existed for two years,
+and been being used by a lot of people. It is also more future-proof and resilient to a variety of
+security bugs.
+== This new thing is too wide ==
+Yes, it is. We fixed this in {{bug|1343663}} which will be deployed on the usual schedule,
+which is weekly on Tuesdays.
+== How can 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.
+of the bug form, as illustrated below, or use the '''Ctrl+E''' keyboard shortcut.
 [[File:BMP-Edit-Button2.png|frameless|A screenshot highlighting the Modal "Edit Bug" button]]
-== How do I Collapse/Expanded Fields ==
+== How do I Collapse/Expand Fields ==
-Click on the drop-down error under the Edit button.
+Click on the drop-down arrow under the Edit button.
 [[File:BMO-Modal-Fields-DropDown.png|frameless|upright=0.75]]
-== How do I Collapse/Expanded Fields by Default? ==
+== How do I Collapse/Expand 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
-[https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_remember_collapsed_row Remember visibility of header sections when viewing a bug] on the user preferences page.
+[https://bugzilla.mozilla.org/userprefs.cgi?tab=settings#ui_remember_collapsed Remember visibility of header sections when viewing a bug] on the user preferences page.
 [[File:BMO-UserPref-Remember visibility of header sections when viewing a bug.png]]
-== The Classic/Dusk Skin Looks Ugly ==
+== Why is the comment box so short? ==
+It will expand to about 25 lines when focused. If this is not the case, go to the user preferences page and make sure [https://bugzilla.mozilla.org/userprefs.cgi#zoom_textareasz Zoom textareas large when in use (requires JavaScript)] is set to "On"
+[[File:BMO-UserPref-Zoom textareas large when in use.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 switching to the Mozilla Skin].
 We will also accept patches for the Classic or Dusk skins, but working on them is not a priority.
 [[File:BMO-UserPref-ChangeSkin.png]]