Silent Update not now prompt: Difference between revisions

Jump to navigation Jump to search

Silent Update not now prompt (view source)

Revision as of 22:51, 29 August 2011

399 bytes added ,  29 August 2011
no edit summary
mNo edit summary
No edit summary
Line 10: Line 10:
}}
}}
{{FeaturePageBody
{{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 takes place in the background, Firefox will alert them that certain Add-ons have become invalid and they have 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 unsupported 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:


1) Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
1) Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
Line 17: Line 17:


2) 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.
2) 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.  
|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 process it also checks for add-ons compatibility and identifies two add-ons that are unsupported with 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 check on a daily basis AMO to see if the specific Add-ons have been updated to become compatible.   
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 unimportant 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.   


There are two scenarios that can take place here:
There are two scenarios that can take place here:


1) 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
1) 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.


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 at least one add-on that is still unsupported, we don't remind or bring up any additional prompts until all add-ons are supported or two weeks have elapsed since the initial update process.   


<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:
<b>Things to note here</b> -- the reason to go down the path of a "required" update 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.
#Based on our data, we have learned over time that 99% of active add-on developers update their add-ons to become compatible with the latest version of Firefox.  Add-ons that are not updated within 2 weeks of a Firefox release in general will not be supported moving forward. 
 
#To reduce product fragmentation and user confusion, our goal is to offer the most secure, feature-rich and optimized browsing experience that continues to move the web forward.  All Firefox users should be offered that opportunity and we're fully aware that certain add-on functionality is critical to users' workflow and will do our best to work with developers to stay updated. 
 
#Users will continue to have the option to turn off 'Updates' in general, but are encouraged to leave that checked so they have the best experience.  Not only will we continue to innovate by delivering new features, but enhancements under the hood like memory reduction/performance/etc. will help create new experiences across the web.


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 unsupported Add-ons (in any).
|Feature requirements=Leveraging the new changes to the Add-on compatibility checker, Firefox will create a new dialog showing users all unsupported Add-ons (in any).


Dialog should offer two options:
Dialog should offer two options:
*"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)
*"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)
 
Once two weeks have elapsed, Firefox will automatically update to the latest version in the background without interrupting the user.
 
}}
}}
{{FeatureInfo
{{FeatureInfo
Clee
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/344228"

Navigation menu