Silent Update not now prompt: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 27: Line 27:
2) 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.   
2) 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 the following:
<b>Things to note here</b> -- the reason to go down the path of not forcing our users to upgrade if there are unsupported Add-ons is the following:


1) Mozilla wants to continue to stand by our mission of user sovereignty and choice.  Forcing users to update doesn't offer them this choice.
1) Mozilla wants to continue to stand by our mission of user sovereignty and choice.  Forcing users to update doesn't offer them this choice.
2) 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.
2) 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 all (if there are any) unsupported Add-ons
*Dialog should offer two options:
 
*1) "Not now" (wait X days and continue to check if there are new updates for the unsupported Add-ons)
Dialog should offer two options:
*2) "Update" (users can manually decide to continue the update since they don't care about the incompatible 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)
}}
}}
{{FeatureInfo
{{FeatureInfo
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits