704483 - When switching the strictCompatibility pref to false, add-ons are displayed as incompatible until an Add-on manager refresh

Status: RESOLVED DUPLICATE of bug 702920

(Toolkit :: Add-ons Manager, defect)

Description

[Virgil Dicu [:virgil] [QA]]

Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111121 Firefox/11.0a1

Have one incompatible add-on installed (e.g. Ubuntu Firefox Modifications)
1. Start Firefox Nightly with the extensions.strictCompatibility pref set to true.
2. Open Add-ons manager.
3. In a separate tab, change the pref to false in about:config.
4. Switch to Add-on Manager tab.

The extension is still listed as incompatible, until refreshing the Add-on manager.

Comment 2

[Virgil Dicu [:virgil] [QA]]

Please note that the summery of bug 702920 refers to disabled add-ons. This covers enabled add-ons that change state after pref change.

Comment 3

[Blair McBride [:Unfocused] (UNAVAILABLE)]

I can't reproduce this. To clarify:

When you refresh the Add-ons Manager, does the addon show the nofication "ADDON-NAME will be enabled after you restart Nightly"? And before refreshing, that notification isn't shown?

Comment 4

[Virgil Dicu [:virgil] [QA]]

Blair, before refreshing it is listed as "incompatible with current version of Firefox", after refreshing it is disabled and compatible.

http://www.screencast.com/users/NoIdea1234/folders/Default/media/1e4cadb8-472e-4e19-9b83-8a7592896504

I made a screen cast on Windows with this issue.

Comment 5

[Blair McBride [:Unfocused] (UNAVAILABLE)]

The screen cast shows bug 702920, where the addons that become compatible are disabled (but you can click the button to enable them).

Is it different on Linux? (comment 0 refers to Ubuntu Firefox Modifications)

Comment 6

[Virgil Dicu [:virgil] [QA]]

No, the behavior is the same for Linux.

There are two related issues here. The difference is made by pref toggling direction (true-false, false-true). Will exemplify with Greasemonkey (compatible until Firefox 9): 

a) Non-functional Enable button after toggling the pref to true (until a refresh)
1. Start F9 with clean profile.
2. Install and disable Greasemonkey.
3. Upgrade to F11 
4. While Add-on Manager is open (the pref is set to false by default) (Greasemonkey is compatible and disabled), toggle the pref to true.
5. Result: Enable button has no functionality until refresh

b) Add-on listed as incompatible after toggling the pref to false until a refresh
1. Start F9 with clean profile.
2. Install Greasemonkey.
3. Upgrade to F10 
4. While Add-on Manager is open (the pref is set to true) (Greasemonkey is incompatible and thus disabled), toggle the pref to false.
5. Result: Greasemonkey is still listed as incompatible until a refresh.

I'll mark this as a duplicate of bug 702920 and will note to myself to check both issues when that is resolved.