In this scenario, you likely won’t notice that Firefox has applied an update as no UI is shown. The next time that Firefox starts up, the existing installation is swapped with the new updated installation which is ready to be used. Instead of staging the update itself, an entire updated version of Firefox is staged. When Firefox finishes downloading an update, it launches the updater application in the background without displaying any UI, and applies the update in a new directory that is completely separate from the existing installation directory. Here’s a short version of how the fix works. The technical details of how I’m fixing this problem can be found this document. The goal of my project is to minimize the amount of time it takes for Firefox to launch after downloading an update.
This is clearly less than ideal.įor the past few weeks, I have been working on a project to improve this process. All of this happens as you’re waiting for your browser to start up in order to do what you wanted to do. When the update process is finished, the updater program restarts Firefox. If an update ready to be applied is found, Firefox launches the updater program, and applies the update on top of the existing installation (showing that progress bar as it’s doing its job). The next time that Firefox is about to start up, it checks out the staging directory. When the update is downloaded, Firefox stages it in a directory ready to be applied. In order to update itself, Firefox first starts to download an update in the background. It displays while Firefox completes the update process after a new version is installed and the browser is restarted.
0 kommentar(er)
