Silent Update not now prompt: Difference between revisions

Jump to navigation Jump to search

Silent Update not now prompt (view source)

Revision as of 23:27, 21 November 2011

No change in size ,  21 November 2011
no edit summary
No edit summary
No edit summary
Line 21: Line 21:
There are a few things to note here:
There are a few things to note here:


#If both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened.   
*If both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully, Sandra will be able to continue to user Firefox as if nothing happened.   
#Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks.  She has the option to "remind me later".
*Sandra continues to have at least 1 incompatible add-on on the final day of the grace period and Firefox will prompt her to update at that point with some language "warning" language that her browser is not secure and she could be vulnerable to attacks.  She has the option to "remind me later".
#If she selects "remind me later", Firefox will defer for 7 additional days and on day 14, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible.  Firefox informs her that X add-ons were disabled due to security reasons.   
*If she selects "remind me later", Firefox will defer for 7 additional days and on day 14, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible.  Firefox informs her that X add-ons were disabled due to security reasons.   


<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:
<b>Things to note here</b> -- the reason to go down the path of a "required" update is the following:


#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.  
*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.  
#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.   
*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.
*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.
|Feature requirements=#All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date
|Feature requirements=*All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date
#For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
*For users with 1 or more incompatible Add-ons, we will offer a 7-day grace period with no prompt to update Firefox (assuming this passes security review)
#As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
#As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 7-day grace period when all of their incompatible Add-ons become compatible
#On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
*On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
**"Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks.  We will disable all incompatible add-ons (we will not remove them) at the time of updating.
**"Update now" -- We ask users to update now and inform them that their browser is insecure and they are more vulnerable to attacks.  We will disable all incompatible add-ons (we will not remove them) at the time of updating.
**"Remind me later" -- We will defer the update for one additional week and on day 14, we will update users automatically.  However, we will notify users that we will be disable X add-on due to security reasons.  (via drop-down or door hanger modules)
**"Remind me later" -- We will defer the update for one additional week and on day 14, we will update users automatically.  However, we will notify users that we will be disable X add-on due to security reasons.  (via drop-down or door hanger modules)
#The team is well aware this feels a bit heavy-handed, but we take security very seriously.  For users who still would like to control whether they are "auto-updated" when there are incompatible add-ons, the requirement here is to create an additional option within the pref menu to allow users to turn off "auto-updates for security reasons".   
*The team is well aware this feels a bit heavy-handed, but we take security very seriously.  For users who still would like to control whether they are "auto-updated" when there are incompatible add-ons, the requirement here is to create an additional option within the pref menu to allow users to turn off "auto-updates for security reasons".   
#The UX team will follow-up with these requirements and provide visual specs on what the new prompt looks like and its exact behavior.
*The UX team will follow-up with these requirements and provide visual specs on what the new prompt looks like and its exact behavior.
}}
}}
{{FeatureInfo
{{FeatureInfo
Clee
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits

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

Navigation menu