MozillaWiki

Silent Update not now prompt: Difference between revisions

Page Discussion

Silent Update not now prompt (view source)

Revision as of 03:14, 27 August 2012

1,566 bytes added ,  27 August 2012
no edit summary
No edit summary
No edit summary
 
(23 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{FeatureStatus
{{FeatureStatus
|Feature name=Silent Update: New workflow for updating users with incompatible add-ons
|Feature name=Silent Update: Updated workflow for users with incompatible add-ons
|Feature stage=Definition
|Feature stage=Planning
|Feature status=In progress
|Feature status=In progress
|Feature health=OK
|Feature health=OK
|Feature status note=Robert following up with UX to finalize some timing specs.
|Feature status note=Other work has been prioritized ahead of this feature. This work is currently untargeted.
Team met with UX to review use cases and the specs have been updated to reflect the latest plan. Feature page is ready for development.
}}
}}
{{FeatureTeam
{{FeatureTeam
Line 11: Line 12:
|Feature lead engineer=Robert Strong
|Feature lead engineer=Robert Strong
|Feature qa lead=Ioana Budnar
|Feature qa lead=Ioana Budnar
|Feature ux lead=Alex Limi
}}
}}
{{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 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:
|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.


#Continue with the upgrade (more secure, latest features, etc.) because the invalid add-ons are not important to the user.
*{{bug|715607}}
#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 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.  


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.   
Given there are incompatible add-ons, Firefox will not update Sandra to the latest version of Firefox and enter a 10 day grace period that will continue to check in the background if her incompatible add-ons become compatible.   


There are two scenarios that can take place here:
There are a few things to note here:


#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.
*If both add-ons become supported within the 10 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.
#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? (TBD) weeks have elapsed since the initial update process.   
*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 10 additional days and on day 20, Firefox will automatically update her to the latest version and disable any add-ons that continued to be incompatible.  Firefox informs her via the notification bar that certain add-ons were disabled due to a Firefox security update.   


<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. Add-ons that are not updated within 2(?) weeks of a Firefox release in general will not be supported moving forward. (we should get hard data from Fligtar on this.) 
*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=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=*All users without Add-ons or have all compatible Add-ons are updated to the latest version of Firefox on release date
 
** ITYM "eligible to update, modulo checking frequency and [https://wiki.mozilla.org/Firefox/Features/Lessen_App_Update_Displayed_UI prompts for long sessions]" -Jesse
Dialog should offer two options:
*For users with 1 or more incompatible Add-ons, we will offer a 10-day grace period with no prompt to update Firefox (assuming this passes security review)
#"Update" (users can manually decide to continue the update since they don't care about the incompatible Add-ons)
*As Add-ons become compatible on subsequent days post release, users will auto update anytime within the 10-day grace period when all of their incompatible Add-ons become compatible
#"Not now" (wait X days and continue to check if there are new updates for the unsupported Add-ons)
*On the 10th 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.
Once two weeks have elapsed, Firefox will automatically update to the latest version in the background without interrupting the user. (this is still an area open for discussion. -Asa)
**"Remind me later" -- We will defer the update for 10 additional days and on day 20, we will update users automatically.  However, we will notify users via the notification bar with the following message:
***"For security reasons, Firefox has been upgraded, but certain add-ons have been disabled. Please contact the add-on authors for more info. [Link to add-ons manager]"
*Some additional requirements we discussed:
**In the preferences dialog under Advanced > Update, remove the "never check for updates" radio button option.
**In the preferences dialog under Advanced > Update, remove the "Warn me if this will disable any of my add ons" check box.  Now that we've moved to add-ons default to compatible, the only add-ons that will be incompatible are ones with binary components.  This logic should be included in the 'recommended' update selection.
**Create an add-on that allows users who want to have the option to disable the ability for Firefox check for updates.
}}
}}
{{FeatureInfo
{{FeatureInfo
Line 49: Line 56:
}}
}}
{{FeatureTeamStatus
{{FeatureTeamStatus
|Feature qa status=Active
|Feature security status=sec-review-needed
|Feature security health=Assigned
|Feature security notes=imelven is embedded here and should look at this first
|Feature qa status=In progress
|Feature qa notes=[https://wiki.mozilla.org/Silent_Update_not_now_prompt/TestPlan Test Plan]
|Feature qa notes=[https://wiki.mozilla.org/Silent_Update_not_now_prompt/TestPlan Test Plan]
}}
}}
LawrenceMandel
Confirmed users
2,473

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/363581...464211"