Inline Installation of Firefox Extension

Chirag Shah

By Chirag Shah

on September 27, 2018

Inline Installation

Firefox extensions, similar to Chrome extensions, help us modify and personalize our browsing experience by adding new features to the existing sites.

Once we've published our extension to the Mozilla's Add-on store(AMO), users who browse the AMO can find the extension and install it with one-click. But, if a user is already on our site where a link is provided to the extension's AMO listing page, they would need to navigate away from our website to the AMO, complete the install process, and then return back to our site. That is a bad user experience.

The inline installation enables us to initiate the extension installation from our site. The extension can still be hosted on the AMO but users would no longer have to leave our site to install it.

We had to try out a few suggested approaches before we got it working.


InstallTrigger (Link is not available) is an interface included in the Mozilla's Apps API for installing extensions. Using JavaScript, the install method of InstallTrigger can be used to start the download and installation of an extension (or anything packaged in a .xpi file) from a Web page.

A XPI(pronounced as "zippy") is similar to a zip file, which contains manifest file and the install script for the extension.

So, let's try to install the Grammarly Extension for Firefox. To use it, we first need its .xpi file's location. Once we have published our extension on the AMO, we can navigate to the listings page for it and get the link for the .xpi.

For our present example, here's the listing page for Grammarly Extension.

Here, we can get the .xpi file's location by right clicking on the + Add to Firefox button and clicking on Copy Link Location. Note that the + Add to Firefox button would only be visible if we browse the link on a Firefox browser. Otherwise, it would be replaced by a Get Firefox Now button.

Once we have the URL, we can trigger the installation via JavaScript on our web page.

2  "Name of the Extension": {
3    URL: "url pointing to the .xpi file's location on AMO",
4  },

Pointing to the latest version of the Extension

When we used the URL in the above code, the .xpi file's URL was specific to the extension's current version. If the extension has an update, the installed extensions for existing users would be updated automatically. But the URL to the .xpi on our website would be pointing to the older version. Although the old link would still work, we would always want new users to download the latest version.

To do that, we can either fetch the listing page in the background and parse the HTML to get the latest link. But that approach can break if the HTML changes.

Or we can query the Addons Services API, which returns the information for the extension in XML format.

For the Grammarly Extension, we first need its slug-id. We can get it by looking at its listing page's URL. From, we can note down the slug which is grammarly-1

Using this slug id, we can now get the extension details using It returns the info for the Grammarly Extension. What we are particularly interested in is the value in the <install> node. That is what the desired value is for the latest version for our .xpi.

Let's see how we can implement the whole thing using React.

1import axios from "axios";
2import cheerio from "cheerio";
5  "";
8export default class InstallExtension extends Component {
9  state = {
10    grammarlyExtensionUrl: FALLBACK_GRAMMARLY_EXTENSION_URL,
11  };
13  componentWillMount() {
14    axios.get(URL_FOR_FETCHING_XPI).then((response) => {
15      const xml =;
16      const $ = cheerio.load(xml);
17      const grammarlyExtensionUrl = $("addon install").text();
18      this.setState({ grammarlyExtensionUrl });
19    });
20  }
22  triggerInlineInstallation = (event) => {
23    InstallTrigger.install({
24      Grammarly: { URL: this.state.grammarlyExtensionUrl },
25    });
26  };
28  render() {
29    return (
30      <Button onClick={this.triggerInlineInstallation}>
31        Install Grammarly Extension
32      </Button>
33    );
34  }

In the above code, we are using the npm packages axios for fetching the xml and cheerio for parsing the xml. Also, we have set a fallback URL as the initial value in case the fetching of the new URL from the xml response fails.

Stay up to date with our blogs. Sign up for our newsletter.

We write about Ruby on Rails, ReactJS, React Native, remote work,open source, engineering & design.