Comment 2 for bug 915895

Chris Coulson (chrisccoulson) wrote :

Migrating extensions to be profile-managed is something that we're only doing in Lucid and Maverick so that we don't have to keep a dozen or so extensions updated for the next year. In any case, those are also disabled by default and trigger the about:newaddon tab after installing them. I'd prefer for this to not be a long term thing, as the addon migrator code is quite sensitive to behavioural changes in the addon manager, making it difficult to support for 5 years (but it's manageable with the 1 year of support left for Lucid)

The issue is that Firefox considers anything that isn't installed via its addon manager as third party (see blog.mozilla.com/addons/2011/08/11/strengthening-user-control-of-add-ons/).

We do make an exception though for the addons that are bundled on the CD though.

Personally, I would prefer it if mozvoikko was hosted on addons.mozilla.org now so that users could install it from there rather than the archive. When we dropped all of the Firefox extensions from the archive, we made an exception for mozvoikko because it contained a binary component. This isn't the case anymore though (it's all written in JS), so there doesn't seem to be any real reason to make an exception for it now (other than the fact that the developers haven't submitted it to addons.mozilla.org).