Community
Participate
Working Groups
When updates are available, an update button appears in the tool bar. When the updates are first discovered, the repos are loaded and pushing this button is really fast. But if you wait awhile before pushing this button, the repos are likely not loaded anymore, and pushing the button causes a long (hourglass) wait. We need to load in the background in this case, or else have the update button hang onto the repo references in order to keep them alive.
Hanging onto the references sounds dangerous - the user may never click the button during that session.
marking M6, as that is when I'll look at moving all actions into handlers (and the background loading code in the handlers can be used here).
This was fixed as part of the work for bug 268205 and some wizard reorg. The update plan is computed in the background by the automatic updater, and any loading of repos that needs to happen then, happens. On a profile change, we recompute the updates in the background, and if there are still updates, we compute a new plan in the background. When the popup or update button is pressed, the wizard immediately opens with the precomputed plan. If the user changes the update selections, *then* it is possible that a new plan would need to be computed and repos would have to be reloaded, but this is true for all wizard workflows.
