Addons re-enable without prompting




9 years ago
9 years ago


(Reporter: J. Warren, Unassigned)


1.9.0 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)




9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/2008120122 Firefox/3.0.5

After disabling default addons: Microsoft DRM (both), RealPlayer (both), and WGA plugins, all will reenable themselves WITHOUT prompting on the part of the user.


Reproducible: Always

Steps to Reproduce:
1. Disable the addons/plugins.
2. Periodically check to see their status is still disabled.
Actual Results:  
All the default/addon-plugins will re-enable themselves WITHOUT prompting on the part of the user.


Expected Results:  
Remain in the disabled state.


Remained in the disabled state.

Component: Preferences → Plug-ins
Product: Firefox → Core
QA Contact: preferences → plugins
Version: unspecified → 1.9.0 Branch

Comment 1

9 years ago
Don't have enough info, but the effect is similar to bug 471245. See if you can avoid the re-enabling by disabling one or more of your extensions.

Comment 2

9 years ago

Yeah, did all that - 'still fails.

'Will attempt to localize to one particular plug-in of the many default ones installed... 'would be nice if at least one other human being would attempt confirmation...

Create a new profile, see if bug 471245 is the same thing.

Comment 4

9 years ago
Found bug is caused by Foxit Reader 3.0 build 1301, which shows addon as installed in FF v3.0.5, and apparently causes other addons to re-enable after being disabled. 

Previous build Foxit Reader 3.0 Build 1222 works OK, except it does NOT show addon installed in FF v3.0.5 >Tools >Addons .


Comment 5

9 years ago
I tried to reproduce this and it seems to work fine for me. Maybe some other factors involved? Installation of Foxit Reader 3.0 in a WinXP VirtualBox gave me the "Foxit Reader Plug-In For Firefox and Netscape" plugin and the "Foxit Toolbar" extension. The extension is JAR packed so it doesn't look like this is bug 471245.

In any case, if you've narrowed it down to a single cause add-on (that's not listed on AMO) then please report this problem to them. It might be nice to know why this happens, but without more info there's nothing for anyone here to do. Closing. Post here again if you learn something new.
Last Resolved: 9 years ago
Resolution: --- → INVALID

Comment 6

9 years ago
"...please report this problem to them."

Already done - see:

You need to log in before you can comment on or make changes to this bug.