Silent Update: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 15: Line 15:
With the transition to the Rapid Release development model, the frequency in which we interrupt a user's workflow will be increasingly more common.  With goals to offer a secure, feature-rich, and fun browsing experience, we want to ensure everyone is on the latest version of Firefox.  To achieve this goal, this particular feature will breakdown the necessary pieces to deliver a silent update experience.
With the transition to the Rapid Release development model, the frequency in which we interrupt a user's workflow will be increasingly more common.  With goals to offer a secure, feature-rich, and fun browsing experience, we want to ensure everyone is on the latest version of Firefox.  To achieve this goal, this particular feature will breakdown the necessary pieces to deliver a silent update experience.


Silent Update is comprised of the following 5 components:
Silent Update is comprised of the following 6 components:
 
 
<b>1) Move bulk of update to background before shut down and remove update UI from browser start-up. ([https://wiki.mozilla.org/Silent_Update_updater feature page]):</b>
<b>1) Remove download/update dialog when new Firefox version is available ([https://wiki.mozilla.org/Firefox/Features/Lessen_App_Update_Displayed_UI]):</b>
*Update dialog will no longer be appropriate with Rapid Releases
*This dialog appears during the user's current session and its purpose is only to notify the user that a download is happening in the background
<b>2) Move bulk of update to background before shut down and remove update UI from browser start-up. ([https://wiki.mozilla.org/Silent_Update_updater feature page]):</b>
*Given the download is happening in the background without notifying the user based on 1), this component will shift bulk of the installation process to the user's current session before the restart
*Updater will need to change for Windows, Mac and Linux
*Updater will need to change for Windows, Mac and Linux
<b>2) Add-on compatibility check will default to compatible ([https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature page]):</b>
<b>3) Add-on compatibility check will default to compatible ([https://wiki.mozilla.org/Features/Add-ons/Add-ons_Default_to_Compatible feature page]):</b>
*Modifying how Firefox determines which Add-ons are compatible
*Modifying how Firefox determines which Add-ons are compatible
*This will exclude:
*This will exclude:
Line 25: Line 29:
**All strict incompatible add-ons
**All strict incompatible add-ons
**All blacklisted add-ons
**All blacklisted add-ons
<b>3) What's new page content will transition to other tools and what's new tab will be removed ([https://wiki.mozilla.org/Silent_Update_whatsnew feature page]):</b>
<b>4) What's new page content will transition to other tools and what's new tab will be removed ([https://wiki.mozilla.org/Silent_Update_whatsnew feature page]):</b>
*Dedicated placement in Firefox about:home page (being explored)
*Dedicated placement in Firefox about:home page (being explored)
*Hover panel from from somewhere on the page (being explored)
*Hover panel from from somewhere on the page (being explored)
*Brainstorm with UX/Marketing
*Brainstorm with UX/Marketing
<b>4) Firefox updates need to bypass OS permissions dialog ([https://wiki.mozilla.org/Silent_Update_OS_Dialogs feature page]):</b>
<b>5) Firefox updates need to bypass OS permissions dialog ([https://wiki.mozilla.org/Silent_Update_OS_Dialogs feature page]):</b>
*Win7 UAC (user account control) dialogue
*Win7 UAC (user account control) dialogue
*Mac OS: determine if there are issues for non-admins
*Mac OS: determine if there are issues for non-admins
<b>5) Update the add-on compatibility check prompt ([https://wiki.mozilla.org/Silent_Update_not_now_prompt feature page]):</b>
<b>6) Update the add-on compatibility check prompt ([https://wiki.mozilla.org/Silent_Update_not_now_prompt feature page]):</b>
*In conjunction with component (2), when the update process encounters an incompatible add-on we should prompt with a dialog providing users the options of "not now" or "remind me later".
*In conjunction with component (2), when the update process encounters an incompatible add-on we should prompt with a dialog providing users the options of "not now" or "remind me later".
}}
}}
canmove, Confirmed users, Bureaucrats and Sysops emeriti
496

edits