User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 We have 10,000 enterprise companies who are frustrated trying to use Firefox because they get no help installing our NPAPI plugin for the DreamFactory Player. All they see is a message "no suitable plugins were found" which is not true -- our MIME type "application/dreamfactory" is registered with IANA. Internet Explorer handles this situation seamlessly, even with UAC. These customers WANT to install the plugin, please help the plugin finder service find our installer. Other than this we work great with Firefox. Reproducible: Always Steps to Reproduce: 1. Go to http://www.dreamfactory.com/projects/bootfile.html 2. See the confusing and incorrect messages 3. Stop using Firefox and go use Internet Explorer for automatic installation Expected Results: Tell them a suitable plugin WAS found, and give them the option to install it. I am the CTO at DreamFactory Software email@example.com PLEASE fix this, we want our customers to continue using Firefox
1. The correct IANA MIME type is "application/vnd.dreamfactory", it was missing the "vnd." tree prefix. See URL below. http://www.iana.org/assignments/media-types/application/vnd.dreamfactory 2. I verified the described steps to reproduce this behavior. 3. On the Plugin Check / More Info page ( http://www.mozilla.com/en-US/plugincheck/more_info.html ) I found these instructions: Plugin vendors can _update_their_release_information. (link: firstname.lastname@example.org ) Maybe try that? Personal note: I'm just a casual Mozilla Firefox user here on Mozilla Firefox 6.0b4. Just learning about the whole unidentified plugins issue in general, as I have several installed from large vendors such as Google, Apple, Yahoo, NVIDIA, and a free software project GPAC. All of them are not recognized.
PFS is being retired, and there are no plans to support the installation of additional plugin types (due to history of stability, performance, and security problems plugins introduce). Websites using these plugins should provide their own install information when the plugin is missing or migrate to HTML-based solutions.