Silent Update not now prompt: Difference between revisions

Silent Update not now prompt (view source)

Revision as of 17:32, 26 August 2011

139 bytes removed , 26 August 2011

no edit summary

Clee

canmove, Confirmed users, Bureaucrats and Sysops emeriti

496

edits

@@ Line 10: / Line 10: @@
 }}
 {{FeaturePageBody
-|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], users who have Add-ons that are unsupport when a silent update is taking place in the background, Firefox will alert them that certain Add-ons have become invalid and they have one of two options:
+|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], users who have Add-ons that are unsupport when a silent update takes place in the background, Firefox will alert them that certain Add-ons have become invalid and they have two options:
 ) Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
+OR
 ) User can select "not now" and wait X days for the Add-on developers to update their code to become compatible with the latest version of Firefox.
+|Feature users and use cases=Sandra is using Firefox to check her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox runs through the installation it also checks for Add-ons, it identifies two Add-ons that are unsupported with the new version of Firefox.
-The requirement here is to create/modify a dialog prompt that communicates these options.
+There is a prompt that surfaces to Sandra informing her of the new update and which Add-ons are unsupported.  She is given two options to 1) continue with the update and ignore the Add-ons because they are irrelevant to her or 2) select "not now" where Firefox will check on a daily basis AMO to see if the specific Add-ons have been updated to become compatible.
-|Feature users and use cases=Sandra is using Firefox checking her email and at the same time in the background, Firefox is being updated to the latest version.  However, as Firefox makes all the appropriate checks such as for Add-ons, it identifies 2 Add-ons that are unsupported on the new version of Firefox.
-There is a prompt that surfaces to Sandra informing her of the new update and which Add-ons are unsupported.  She is given two options to 1) continue with the update and ignore the Add-ons because they are irrelevant to her or 2) select "not now" where Firefox will not check on a daily basis AMO to see if he specific Add-ons have been updated to be compatible.
 There are two scenarios that can take place here:
@@ Line 25: / Line 25: @@
 ) Both Add-ons become supported over the next couple days and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market
-) Zero or 1 of 2 Add-ons become supported, but because the one Add-on that still isn't supported since the initial "update" process, we don't remind or bring up any additional prompts until all Add-ons are supported or the next Firefox update becomes available.
+) Zero or one of two Add-ons become supported, but because there's one add-on that is still unsupported, we don't remind or bring up any additional prompts until all Add-ons are supported or the next Firefox update becomes available.
-*Things to note here -- the reason to go down the path of not forcing our users to upgrade if there are unsupported Add-ons is because:
-) Mozilla wants to continue to stand by our mission of user sovereignty and user choice.  Forcing users to update doesn't offer them this choice.
+*Things to note here -- the reason to go down the path of not forcing our users to upgrade if there are unsupported Add-ons is the following:
-) Although our goal of updating users is primarily around ensuring a safe, secure web browsing experience, some users are comfortable making the trade-off of not being secure for functionality that is important to them.  If we force an update and break certain functionality that defines their web experience, we may push them away from Firefox all together.  The end result may be users who a) leave Firefox for Chrome/Safari/IE and b) continue to be insecure (threat to others and themselves without knowing it) because they need and expect the functionality the Add-on previously offered them.
+) Mozilla wants to continue to stand by our mission of user sovereignty and choice.  Forcing users to update doesn't offer them this choice.
+) Although our goal of updating users is primarily around ensuring a safe, secure web browsing experience, some users are comfortable making the trade-off of not being secure for functionality that is important to them.  If we force an update and break certain functionality that defines their web experience, we may push them away from Firefox all together.  The end result may be users who a) leave Firefox for Chrome/Safari/IE and b) continue to be insecure (threat to others and themselves without knowing it) because they need and expect the functionality the Add-on previously offered them.
+|Feature requirements=*Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users all (if there are any) unsupported Add-ons
-|Feature requirements=*Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users any/all unsupported Add-ons
 *Dialog should offer two options:
-) Not now (wait X days and continue to check if there are new updates for the unsupported Add-ons)
+) "Not now" (wait X days and continue to check if there are new updates for the unsupported Add-ons)
-) Update (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
+) "Update" (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
-*Placeholder, more reqs coming
 }}
 {{FeatureInfo