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:26, 21 November 2011

555 bytes added ,  21 November 2011
no edit summary
No edit summary
No edit summary
Line 14: Line 14:
}}
}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation.  We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.
|Feature overview=Related to the Add-ons Compatibility Check [https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature], Firefox will need to carefully handle each user's experience differently depending on their add-on compatibility situation.  We have carefully outlined the requirements here that determine how Firefox should work based on a user's scenario.
 
|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.  
|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.  


Line 22: Line 21:
There are a few things to note here:
There are a few things to note here:


#Both add-ons become supported within the 7 day grace period and the Firefox update happens in the background successfully and Sandra is able to use the most secure, full-feature browser in the market.
#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 skip the update process this release and wait for the next release to update.
#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".
#This check will go on for Sandra for every Firefox release.  However, if she reaches 3 consecutive releases where 1 or more incompatible add-on does not become compatible in the 7 day grace period after the release date, Firefox will prompt Sandra and let her know that Firefox will be updated even with an incompatible add-on.   
#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:
Line 34: Line 33:
#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 skip updating the user for this release and wait for the N+1 release
#On the 7th day of the grace period if there are still incompatible Add-ons, we will prompt the user with the two options:
#For users who have incompatible Add-ons for 3 consecutive release, we will display the incompatible Add-on prompt on the 7th day of the 3rd release where they've had incompatible Add-ons and inform users that we are auto-updating them regardless of the incompatible Add-on (this has been approved by both Product and UX teams)
**"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.
#We will update today's incompatible Add-on prompt with a more positive tone (UX to provide specs below)
**"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 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/371915"

Navigation menu