canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Firefox/Input/Standalone Feedback Button: Difference between revisions
Firefox/Input/Standalone Feedback Button (view source)
Revision as of 18:34, 10 July 2011
, 10 July 2011need a "user engagement" roadmap option, will add and update in a sec
m (clearing in prep for migration to new feature page format (will be done momentarily)) |
m (need a "user engagement" roadmap option, will add and update in a sec) |
||
| Line 1: | Line 1: | ||
{{FeatureStatus | |||
|Feature name=Provide a standalone feedback button | |||
|Feature stage=Development | |||
|Feature status=In progress | |||
|Feature health=OK | |||
|Feature status note=Patch Incoming | |||
}} | |||
{{FeatureTeam | |||
|Feature feature manager=Aakash Desai | |||
|Feature lead engineer=Jono Xia | |||
|Feature qa lead=Vlad Ghetiu (irc: vladg) | |||
}} | |||
{{FeaturePageBody | |||
|Feature open issues and risks=* The code in Test Pilot currently looks at ''every'' loaded URL to see whether or not it's an Input website where data is to be filled in. This may be a performance issue, so we should test its impact and replace it with something more efficient if needed. | |||
* If the user has manually placed the Feedback button, should that preference override the channel setting? (I.e. the customization remains even if you switch channels?) | |||
|Feature overview=The Feedback button (which is currently added to the toolbar in the Firefox aurora/beta branches by the bundled Test Pilot add-on) will be moved into Firefox where it becomes part of the default Toolbar Customization panel. | |||
It will need to be added to the toolbar by default on Nightly, Aurora and Beta builds. On Release builds it would not be added by default but the user could choose to add it through the Customization panel. | |||
The button holds a drop-down menu containing two items, "Firefox made me happy because..." and "Firefox made me sad because...", both of which go to the Input website and pre-fill some fields. | |||
<table class="fullwidth-table"> | |||
<tr> | |||
<td style="background-color: #efefef;">Menu Item</td> | |||
<td style="background-color: #efefef;">URL</td> | |||
</tr> | |||
<tr> | |||
<td>Firefox made me happy because...</td> | |||
<td>http://input.mozilla.com/happy</td> | |||
</tr> | |||
<tr> | |||
<td>Firefox made me sad because...</td> | |||
<td>http://input.mozilla.com/sad</td> | |||
</tr> | |||
</table> | |||
'''Ride-Along''' | |||
The URL attached to the "Submit Feedback..." menu item in the Help Menu is [http://mxr.mozilla.org/mozilla-central/source/browser/base/content/utilityOverlay.js#471 hard-coded into the codebase], it'd be good to change it into a pref for testing purposes. | |||
'''Externalities''' | |||
# The Test Pilot add-on (both the AMO version and the bundled-with-Firefox-betas version) must be modified to work with the new standalone Feedback button. This means the add-on no longer creates the Feedback button; instead it looks at the toolbar to see whether there's a Feedback button there, adding the "All your user studies" and "turn on/off user studies" menu items to the button if present, providing an alternate interface otherwise. | |||
# The following strings will need to be localized to something that's not unreasonably long in any language: | |||
#* "Feedback" | |||
#* "Firefox made me happy because..." | |||
#* "Firefox made me sad because..." | |||
|Feature users and use cases=* Users who wish to keep providing Input about Firefox through the feedback button should be able to do so even on the release channel with no bundled add-ons. | |||
* The Test Pilot add-on should be independent of the Feedback button implementation (which allows Test Pilot to become a restartless add-on). | |||
* Input's "/feedback" page should be referred as a pref | |||
|Feature requirements='''Instancing the "Feedback" button''' | |||
# On Nightly/Aurora/Beta builds, a button which opens a menu consisting of two options (i.e. "Firefox made me happy because..." and "Firefox made me sad because...") should be visible on the right hand side of the navigation toolbar by default. | |||
# On Release builds, the button should NOT be visible in the navigation toolbar. But it should be available within the toolbar customization palette to add to the browser UI. | |||
#* If the user is running a "Beta" build, but chooses to remove the Feedback button through customization, it must not reappear on restart. | |||
#* Switching channels must be supported -- The Feedback button has to appear when switching to Beta/Aurora and disappear when switching to Release. (Unless the user has manually modified its location, in which case the modification sticks regardless of channel?) | |||
'''Using the menu items''' | |||
# When either menu item is selected, the appropriate URLs should load and desired information should be pre-filled onto the page (i.e. URL field will include the URL of the previously loaded tab and user agent will be pre-loaded onto a hidden form field). | |||
|Feature non-goals=# Placing the feedback button onto the navigation toolbar by default across all channels/builds. | |||
# Landing Test Pilot as a patch onto mozilla-central. | |||
|Feature qa review=TODO - Any and all test plans and strategies. Either inline or linked to. | |||
|Feature implementation notes=* {{bug|649156}} - Add the feedback button to the customize toolbar palette | |||
==== Next steps ==== | |||
* Separate Feedback button code from Test Pilot add-on and turn it into a patch against mozilla-central (Jono Xia) | |||
}} | |||
{{FeatureInfo | |||
|Feature priority=P1 | |||
|Feature roadmap=Firefox Desktop | |||
|Feature list=Desktop | |||
|Feature engineering team=Desktop front-end | |||
}} | |||
{{FeatureTeamStatus | |||
|Feature products status=tbd | |||
|Feature engineering status=tbd | |||
|Feature security status=tbd | |||
|Feature privacy status=tbd | |||
|Feature localization status=tbd | |||
|Feature accessibility status=tbd | |||
|Feature qa status=tbd | |||
|Feature ux status=tbd | |||
}} | |||