Closed Bug 262067 Opened 21 years ago Closed 20 years ago

Plugin bar does not disappear once the missing plugin has been installed

Categories

(Toolkit Graveyard :: Plugin Finder Service, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Athropos, Assigned: doronr)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040928 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040928 Firefox/0.10 After having installed a zipped nightly, if I go to the given url, I get a bar telling me that a plugin is missing (flash). If I click on the location where the plugin is used and follow the indications, the plugin is correctly installed but the bar does not disappear. Reproducible: Always Steps to Reproduce: 1. Unzipped a nighly in any directory 2. Go to the given url 3. Click on the location where the flash plugin is used 4. Follow the instructions and install the plugin 5. After the installation, the page is reloaded and the plugin is used Actual Results: The bar stays opened Expected Results: The bar should have been closed
Component: General → Plugin Finder Service
Confirming.
Assignee: firefox → doronr
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: firefox.general → firefox.plugin.finder
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0? → blocking-aviary1.0-
I can confirm this is still present in 1.0rc1. Would be nice having this fixed, it seems to be easy to me. sending an internal signal (which should kinda like someone pressed that specific button a second time).
Flags: blocking-aviary1.0- → blocking-aviary1.0+
Yes, this should be fixed before 1.0 final, this could really confuse new users (It even confused myself lol)
Reverting blocking-aviary1.0 back to -. Lieven, please don't change blocking flags set by developers. (In reply to comment #2) > Would be nice having this fixed, it seems to be easy to me. > sending an internal signal (which should kinda like someone pressed that > specific button a second time). If you have a fix, create a patch and attach it to this bug. http://www.mozilla.org/hacking/life-cycle.html
Flags: blocking-aviary1.0+ → blocking-aviary1.0-
wfm If still an issue, reopen with exact steps.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
Product: Toolkit → Toolkit Graveyard
You need to log in before you can comment on or make changes to this bug.