User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:184.108.40.206) Gecko/20071127 Firefox/220.127.116.11 Mnenhy/0.7.5.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20071127 Firefox/22.214.171.124 Mnenhy/0.7.5.0 In Firefox 3.0b2 when trying to install a plugin packaged as an XPI the install fails with error code -244 (unsupported package). It's possible that XPI packages using install.js rather than install.rdf are not supported anymore, but I couldn't find any documentation of this. Reproducible: Always Steps to Reproduce: 1. Try installing Adobe Reader (http://www.adobe.com/products/acrobat/readstep2.html). 2. Allow the XPI to attempt to install. Actual Results: The install fails with "unsupported package" -244. Expected Results: It should have installed properly.
Yes that is correct, xpi packages using install.js are no longer supported.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
This is by design, was implemented in bug 401624, and is documented at http://developer.mozilla.org/en/docs/Updating_extensions_for_Firefox_3
Thanks for the info, I completely missed the note on removing support for install.js. It's seems like there isn't a clean way to package a plugin now that install.js isn't supported in FF3 and there is no longer a plugin value for <em:type> in the install manifest specification (at least that's my understanding from reading over http://developer.mozilla.org/en/docs/Install_Manifests#type ).
You can package your plugin in an ordinary extension; there's really no difference between that and the special em:type
You need to log in before you can comment on or make changes to this bug.