Firefox/Projects/Extension Manager Redesign/design: Difference between revisions

Firefox/Projects/Extension Manager Redesign/design (view source)

Revision as of 05:29, 20 May 2010

1,546 bytes added , 20 May 2010

+moar

Jboriss

Confirmed users

954

edits

@@ Line 121: / Line 121: @@
 * [http://docs.google.com/Doc?docid=0Ad7mAOXgEBZyZGRzNnZ3YjRfMThmZ3FoY2Y4dA&hl=en blocklist proposal]
+===Plugin Updates===
+Plugins are the one item in the add-ons manager that can't be silently, automatically updated.  So, we need a way to both notify users that they need to update plugins, and provide a relatively painless way for them to do it.
+Users will discover that they need to update their add-ons via a doorhanger notification that appears when the user restarts once a week or each time the user restarts (whichever happens less).  Dismissing the notification (via a click anywhere else) or pressing "Remind me Later" will dismiss the notification for another week.  Pressing "Update" will take the user to an "Available Updates" pane in their add-ons manager, which will show the plug-ins that have updates available.
+In a perfect world, from this screen the user would be able to install all plug-in updates by clicking "Install Updates."  However, it's unlikely this will be possible (at least in the near future), and users will likely have to update plug-ins individually.  Assuming this is the case, the "Available Updates" pane would show each plugin with a notice similar to those in the Plugin Check online for both the "potentially vulnerable" and "vulnerable" case.
+If plugins can be updated in-line within the add-ons manager like other add-ons, they will be if the user clicks Update Now.  If the plugin requires a download from an external site, the update button will link to the external site where the user can manually download and install the plugin.
+[[File:Plugin manual update in addonsmanager2342.png|800px]]
 ==Other Functionality==