Closed Bug 267942 Opened 20 years ago Closed 20 years ago

add UI or (hidden?) pref to disable plug-in bar but not finder service

Categories

(Firefox :: Settings UI, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 261655

People

(Reporter: will.rickards, Assigned: bugzilla)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2 When I load a page the page loads and then the plug-in bar appears at the top. I would like a pref or UI so that the plug-in bar does not appear at all. But I still want to be able to click the item in the page requiring the plug-in and use the plug-in finder service. Reproducible: Always Steps to Reproduce: 1. Open Site 2. Watch page load and plug-in bar appear 3. Right-Click on plug-in bar Actual Results: No option to hide the bar permanently appeared. In fact no options are there. Expected Results: Given me some UI to hide the bar permanently. At the very least give me a hidden pref in about:config to permanently hide the bar. I have the pref plugin.default_plugin_disabled set to true. I tried setting it to false but it also disabled the plug-in finder service when I click the items. I still want to use the plug-in finder service, just not the plug-in bar.
Wrong Product/Component. Please change it to Firefox/Preferences. And don't forget to check "Reassign bug to owner and QA contact of selected component".
Component: Plug-ins → Preferences
Product: Browser → Firefox
Assignee: nobody → firefox
QA Contact: core.plugins → mconnor
*** This bug has been marked as a duplicate of 261655 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.