Closed Bug 1267594 Opened 9 years ago Closed 8 years ago

Notify user when using a new profile if there are synced add-ons which require restart

Categories

(Toolkit :: Add-ons Manager, defect, P5)

defect

Tracking

()

RESOLVED WONTFIX
Tracking Status
firefox46 --- wontfix
firefox47 --- wontfix
firefox48 --- wontfix
firefox49 --- wontfix
firefox-esr38 --- wontfix

People

(Reporter: JuliaC, Unassigned)

Details

(Whiteboard: triaged)

[Affected versions]: - 38.8.0esr build1 - latest Nightly - latest Aurora - 47.0b1 build1 (20160425095909) - 46.0 build5 (20160421124000) - 45.0.2 build1 (20160407164938) [Affected platforms]: - Mac OS X 10.9.5 - Windows 10 x64 - Ubuntu 14.04 x32 [Steps to reproduce]: 1. - Launch Firefox with a new profile - Log in to Sync using a valid Firefox account 2. - Go to Hamburger Menu > Add-ons > Get Add-ons - Install two add-ons: one that requires restart (e.g. Greasemonkey) and another one that doesn't require restart (e.g. Google Translator). 3. - Launch Firefox with another new profile - log in to Sync using the same Firefox account (step 1) 4. - Go to Hamburger Menu > Add-ons > Extensions - Inspect the two synced add-ons. - Pay attention at all received notifications. [Expected result]: - After step 3, the user is notified about all synced add-ons state (restart notification). [Actual result]: - After step 3, the add-on that requires restart (e.g. Greasemonkey) isn't yet installed, the user have to restart Firefox in order to complete its instalation, but no notification related to this fact is received. This state is visible only after step 4. - The add-on that doesn't require restart (e.g. Google Translator) is succesfully installed. This state is visible, the user being redirected to the post installation add-on's informative page (e.g. http://add0n.com/google-translator.html?version=0.4.6&type=install) after step 3. [Regression range]: - I didn't yet have the time to see whether this is a regression or not, but I'll check it as soon as possible.
This issue is _not a regression_, as it's reproducible all the way back to Fx29.0.
This is similar in that Firefox fails to inform user of a failed (manual) update: https://bugzilla.mozilla.org/show_bug.cgi?id=1269390
restartless is the way we are moving and webextensions does not have this issue
Priority: -- → P5
Whiteboard: triaged
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.