Closed
Bug 672094
Opened 13 years ago
Closed 7 years ago
Addon-Plugins are not loading on first run of the upgraded Firefox
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: manojmarathayil, Unassigned)
Details
Attachments
(1 file)
9.49 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.122 Safari/534.30 Steps to reproduce: In our addon we have two plugins and we noticed Firefox is not loading those plugins on first run after Firefox upgrade/downgrade. Once we restart it again after first run everything works as normal. We also noticed plugins are loading if we fire "about:plugins" on first run. Please find attached sample xpi and html page to check plugin. Steps to reproduce this issue: Method - 1 1. Install FF version-X (say 4.0 or 5.0) 2. Install addon - TestPlugin 3. Open testplugin.html - Everything is fine 4. Install FF version-Y(say 5.0 or 4.0) 5. Open test.html - FF will report "additional plugins are required to display all the media in this page" 6. Close FF and start again 7. Open testplugin.html - Everything is fine Method - 2: 1. Install FF version-X (say 4.0 or 5.0) 2. Install addon - TestPlugin 3. Open testplugin.html - Everything is fine 4. Install FF version-Y(say 5.0 or 4.0) 5. Open testplugin.html - FF will report "additional plugins are required to display all the media in this page" 6. Open another tab and issue "about:plugins" 7. Open testplugin.html in another tab - Everything is fine Actual results: Addon-Plugins are not loading on first run of the upgraded Firefox Expected results: Addon-Plugins should loading on first run of the upgraded Firefox
Updated•13 years ago
|
Component: General → Plug-ins
Product: Firefox → Core
QA Contact: general → plugins
Version: 4.0 Branch → 5 Branch
The sample plugin is npruntime example given in http://mxr.mozilla.org/seamonkey/source/modules/plugin/samples/npruntime/
Comment 2•13 years ago
|
||
Josh/Mossop: I suspect that we are scanning for new plugins before extensions are enabled in the startup process, but I'm not sure about this. Josh, we do scan on every startup, right? Where does that happen?
I don't think we scan on startup every time. To force a scan after installing a plugin you can use the js method "navigator.plugins.refresh".
We are facing this issue when Firefox is upgraded, not when extension upgraded.
I think we need to scan for plugins on first startup after Firefox upgrade.
Updated•7 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•