Why does the plug-in checker pop up every time I open fire fox?
Since yesterday every time I open fire fox the mozilla plug-in checker loads in a tab (in addition to my set home page) . How do I disable this?
被采纳的解决方案
You can correct this issue by forcing the file blocklist.xml to update or wait until Firefox updates the file.
That update will remove the severity="0" flags in the file that cause the problem.
See:
- /questions/832793?page=2#answer-198407
- http://forums.mozillazine.org/viewtopic.php?p=10899869#p10899869
- Bug 663722 - The blocklist output is including severity="0" where it shouldn't be
所有回复 (6)
One solution was to go to about:config and change the plugin settings, although this fixes the issue of the plugin tab it disables flash...which then is another issue. Is there a solution to get rid of the tab with out having it disable flash?
Type about:config in the URL bar and hit Enter.
If you see the warning, you can confirm that you want to access that page.
Pref = plugins.update.notifyUser if it shows as True, double-click that pref to toggle it to False
That pref was new to the Firefox 3.6 version and is present in later versions.
I just tried that...and it still pops up. After I restarted FF I checked to make sure it was still set to false, it was yet the tab still opens when I open FF.
I feel like an explorer user, where things are implemented with no way to say no. That is one of the reasons I use was using Firefox. I don't have time to mess around. Maybe I need to use something else, like Chrome? Fine, warn me once but to have to navigate around this all the time, especially when the darn pages simply gives me an error and "retry".
选择的解决方案
You can correct this issue by forcing the file blocklist.xml to update or wait until Firefox updates the file.
That update will remove the severity="0" flags in the file that cause the problem.
See:
- /questions/832793?page=2#answer-198407
- http://forums.mozillazine.org/viewtopic.php?p=10899869#p10899869
- Bug 663722 - The blocklist output is including severity="0" where it shouldn't be
The issue has seem to have gone away on its own now.