This is part of the flow documented in the flowchart on slide 3 of: https://docs.google.com/presentation/d/1NSqxUiZDUdFrha0TvuNVEV1v2OqmBPc17XaPbzIwWmQ/edit In this flow, when an addon has an update that requires new permissions, a notification is issued that includes the name of the extension and an action that opens the browser on the add-ons manager detail page for the affected extension. The update permissions dialog is immediately displayed. When the dialog is dismissed, the browser remains at the add-ons manager detail page for the extension.
Assignee: nobody → aswan
Priority: -- → P2
Thinking about this one a little further, we've got a bit of a problem here -- extension updates are stored in a temporary directory so if they aren't acknowledged by a user they aren't saved across browser sessions. This is mildly annoying on desktop but on mobile where non-foreground processes can be killed at any time its going to be a much bigger problem I think. That is connected to this bug since we have to consider the scenario where we send a system notification for an extension update but by the time the user selects the action from the notification, the browser process has been killed. We can try to re-download the update at that time, but then what if that fails? Ugh.
Based on comment 1, I don't have any immediate plans to work on this.
Assignee: aswan → nobody
You need to log in before you can comment on or make changes to this bug.