Closed
Bug 264684
Opened 20 years ago
Closed 10 years ago
Plugin finder doesn't refresh correctly on reload
Categories
(Toolkit Graveyard :: Plugin Finder Service, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bzbarsky, Assigned: jst)
References
Details
BUILD: Current branch Firefox nightly
STEPS TO REPRODUCE:
1) Load page that has an <object> for a MIME type we don't support (from
file://)
2) Change the page so that the <object> has a MIME type we _do_ support
3) Reload or shift-reload.
EXPECTED RESULTS: object gets rendered, yellow bar goes away.
ACTUAL RESULTS: object gets rendered, yellow bar does NOT go away.
It looks like session history loads, even ones that refetch from server just
don't cause the plugin finder bar to reinit correctly...
Comment 1•20 years ago
|
||
This is probably a bug in Ben's yellowbar code, it controls when the bar goes.
| Reporter | ||
Comment 2•20 years ago
|
||
Please reassign as appropriate. I couldn't figure out which component fit for this.
Comment 3•20 years ago
|
||
There is a lot of trouble with history stuff being all screwed up right now.
Updated•16 years ago
|
Product: Firefox → Toolkit
Comment 4•10 years ago
|
||
Bug 836415 has now removed the Plugin Finder Service (PFS) from Firefox. As a result, I'm closing all the remaining PFS bugs. If you're getting this bugmail for an ancient PFS bug, the basic summary of the world today is: * NPAPI plugins are a dying technology * PFS was already restricted to assisting with only the 4 most common plugins * Sites commonly provide their own UI for install a required plugin * Mozilla is generally focusing on improving the web platform so that proprietary plugins are not required. (Note that "plugins" are a completely separate from "browser extensions", such at those found on addons.mozilla.org. The latter are not going anywhere, and are not impacted by the removal of PFS.)
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•10 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•