Question unanswered for over 1 year!! Just how does a plugin become "known" to Firefox? How would a Firefox plugin developer get their plugin to be "known?"
This question has been unanswered for over 1 year!
"Exactly how does a plugin become "known" to Firefox?
How would a Firefox plugin developer get their plugin to be "known?" "
These plugins are "unknown" by Firefox v9, yet I've been using them for years in earlier versions.
Yahoo! activeX Plug-in Bridge Facebook plugin Picasa plugin Windows Live Photo Gallery plugin NPWLPG plugin Google Update plugin RealPlayer Version Plugin 12.0.1.669 plugin RealJukebox NS plugin iTunes Application plugin
모든 댓글 (1)
The Plugin developer can file a Bug to get the process to be "known" started here - https://bugzilla.mozilla.org/ - for Mozilla Services.
Mozilla is mainly concerned about the Plugins that are used by the most number of users, and the Plugins that are most exploitable.
Adobe Acrobat Reader, Adobe Shockwave Flash, Oracle / Sun Java, and Quicktime fall into that category. As far as the "unknown" plugins, those either don't pose a security risk to Firefox users or the plugin itself doesn't expose the version number in a manner that the Mozilla Plugin Check page can use to verify the version number being used "on-the-fly" or the version number isn't in the plugin itself.