Firefox/Projects/Plugin Update Referrals: Difference between revisions

← Older edit

Firefox/Projects/Plugin Update Referrals (view source)

Revision as of 20:06, 5 October 2009

726 bytes removed , 5 October 2009

→‎Firefox

Blur

Confirmed users

587

edits

@@ Line 16: / Line 16: @@
 The user would be notified in the following ways:
-* User visits a page with an outdated plugin. The plugin is allowed to load. A notification box is shown in that tab, informing user that the plugin is outdated. There's a "More Info" (or "Get me Updated") button, that takes the user to the page on mozilla.com. This page would list all outdated plugins the user has installed, not just the one that was just used.
+* User visits a page with an outdated plugin. The plugin is allowed to load. A notification box is shown in that tab, informing user that the plugin is outdated. There's an "Update Plugins..." button, that takes the user to the page on mozilla.com. This page would list all outdated plugins the user has installed, not just the one that was just used.
-* When the user manually checks for updates via Help -> Check for Updates, it also checks for outdated plugins. If there are any, provide a link to the mozilla.com page. This would be emphasized more if there is no update to Firefox itself. If there is a Firefox update, show the mozilla.com page automatically after Firefox restarts (only if there are plugins that haven't been warned about before).
+* When the user manually checks for updates via Help -> Check for Updates, and there is no update, it then checks for outdated plugins. If there are any, provide a link to the mozilla.com page.
-** Note: It may be a bad idea to show this page after an update, as it would compete with the What's New/First Run pages. Alternatively, What's New/First Run pages could detect if any plugin is outdated, and show a link to the outdated plugins page as needed.
 * On startup (not after an update), if outdated plugins are detected, open a tab to the outdated plugins page. This would only happen once for a plugin version.
-** Note: This may not be desirable, as per https://bugzilla.mozilla.org/show_bug.cgi?id=511529#c5
-* On the Plugins tab of the extension manager, there would be a "Check for updates" button (or link). Clicking this would open a tab to the outdated plugins page. Additionally, the items for outdated plugins would indicate that they're outdated.
+* On the Plugins tab of the extension manager, there would be a "Check for updates" button. Clicking this would open a tab to the outdated plugins page. Additionally, the items for outdated plugins would indicate that they're outdated.
+Future improvements:
 * When the blocklist service updates from a periodic check and detects an outdated plugin (that hasn't been warned of before), it shows an alert (via the alerts service) informing the users. Clicking on this alert would open a tab to the plugins page on mozilla.com.
@@ Line 30: / Line 31: @@
 = Progress =
-See [https://wiki.mozilla.org/Plugins:PluginCheck Plugins:PluginCheck] for updates on the website and service side of this problem.
+See [[Plugins:PluginCheck]] for updates on the website and service side of this problem.
-See [https://wiki.mozilla.org/Security:ThePluginProblem Security:ThePluginProblem] for some thoughts from Chris Hofmann on the topic.
+See [[Security:ThePluginProblem]] for some thoughts from Chris Hofmann on the topic.
 == Web Site ==
-* https://wiki.mozilla.org/Website/Sprints/PluginProblem
+* [[Website/Sprints/PluginProblem]]
 == Service ==
+morgamic leading.
+* Still under design, [[PFS2|see documentation]]
-* Still under design.  Morgamic leading.
+Server bugs:
+* {{bug|512787}}
+* {{bug|517974}}
 == Partners ==
@@ Line 53: / Line 59: @@
 == Firefox ==
-* Blocklist changes not speced.
+* Landed on 1.9.2
-* Check for update changes not speced.
-* Integration with mozilla.com not speced.
-* Initial experience not speced.
 = Bugs =
-None yet.
+* {{bug|514327}}