Closed
Bug 720337
Opened 12 years ago
Closed 3 years ago
prioritizing of plugin based on the modified date instead of its location
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: vishu.7123, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: I created a plug-in of xyz mime type and placed in the plugin folder. There was already plug-in of same mime type (xyz) whose entry was in the registry. Actual results: Instead of using my plug-in, firefox loaded and used already existing plugin of same mime type. Expected results: Based on the MDN documentation, firefox searches first in plugin folder and then the registry. https://developer.mozilla.org/en/Gecko_Plugin_API_Reference/Plug-in_Basics#How%20Gecko%20Finds%20Plug-ins But if there are two plugins of same MIME type, one in plugin folder and another in registry, then the plugin which is in plug-in folder has to be given highest priority. When I debugged the firefox code, i found that though firefox searches as per the details gives in MDN, but loads/lists the plugin based on the modification date of a plug-in which is a bug as per the MDN documentation.
Component: Untriaged → Plug-ins
Product: Firefox → Core
QA Contact: untriaged → plugins
Comment 1•3 years ago
|
||
Resolving as wont fix, plugin support deprecated in Firefox 85.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
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
•