How is it possible for add-ons to be proprietary

Talk about add-ons and extension development.
New Member
Posts: 1
Joined: February 10th, 2018, 1:31 pm

Post Posted February 10th, 2018, 1:42 pm

As is explained here the XPI format for Firefox add-ons contains in a ZIP archive the source code of the add-on. One would therefore expect that all add-ons distributed with XPI files (as on ) would be open source, since their source code is compelled to be released in this format. However that is not the case. A good example is the well-known Ghostery add-on ... /ghostery/. This rant ... extensions about proprietary add-ons makes it clear add-ons can be and some are proprietary. In fact under point 6 of the Firefox Add-on Distribution Agreement ... /Agreement Mozilla only encourages developers to make add-ons available under open source licenses.

So what's the deal here? If an add-on's source code is released with an XPI file, as it must be in order for any user to be able to install the add-on, how can some add-ons be proprietary?

Return to Extension Development

Who is online

Users browsing this forum: No registered users and 1 guest