Closed ValentinaPC closed 5 years ago
Looks like the browser fires onInstallEnded for the promise to be resolved [1]. Presumably if the resolve handed back the installObj it should be possible to get the needsRestart hint and not show the installed notification or handle it in some different way.
There should also be a message to show that a restart is required for desktop and the android case where the restart required notification is dismissed though that will need UX input for the amo context.
It would be important to make sure any changes here don't cause problems in the disco pane.
Added the needs: ux label to get input on how a restart required should be displayed. If it's something not too intrusive it could probably work for both mobile and desktop cases.
How about a little pill/badge under the short description saying "restart required" in yellow (#E7AB00)?
I like it.
This also relates to https://github.com/mozilla/addons/issues/10245 which is about removing the post-install overlay for android.
See also mozilla/addons#10313 which related to uninstall for the same thing.
Fixing this requires handling the following:
I lowered the priority on this since add-ons that require a restart are so legacy they are legacy legacy.
Also note that the needs restart badge is getting added in https://github.com/mozilla/addons/issues/10560
Closing this as wontfix
Steps to reproduce:
Expected results: A popup notifying the user that the browser needs to be restarted to apply changes is displayed.
Actual results: 2 popups are displayed: one that requires browser restart and one with "Your add-on is ready" message - as if the add-on was installed.
Notes/Issues:
extensions.webapi.testing
set to "true", it only the "browser needs to be restarted" popup is displayed.Verified on FF51(Android 6.0.1). Issue is reproducing on AMO-dev and -stage. Video for this issue: