A "Hello World" Extension Tutorial
All the information you need to get your first Thunderbird extension up and running.
Last updated
Was this helpful?
All the information you need to get your first Thunderbird extension up and running.
Last updated
Was this helpful?
In the first part of this tutorial, we will create a very simple extension, which adds a "Hello World" button to Thunderbird's main toolbar and a click on it will show a Hello, World! popup.
First, we create an empty hello-world project folder for our extension and navigate to it.
Extensions require a manifest.json file that tells Thunderbird a few basic information about the add-on. Let's place the following manifest.json file directly in the hello-world project folder.
browser_actionThe above manifest includes the definition for a browser_action. That is the button we want to add to Thunderbird's main toolbar. The reference to a browser in its name is inherited from the Firefox Browser.
The location of the HTML file loaded by the popup of our browser_action is defined in the browser_action.default_popup key. Let's create a mainPopup directory in the hello-world project folder for everything related to that popup and start with the following popup.html .
The script tag to include popup.js is setting type="module", which loads the script as a top level ES6 module. This enables the script to use the await keyword in file scope code and to load other ES6 modules.
We will not use these features in this step of the tutorial, but we still use the modern ES6 module approach here to introduce it as a standard programming practice.
We're going to create the following file called popup.js and place it in the same folder as the popup.html file.
What our little script does is sending a message to the console each time we click on our "Hello World" toolbar button. We'll take a look at that in a moment when we try out our add-on. The first line is just a comment, so we can remember what our code is doing.
Now we want to create the CSS file referenced in our HTML file. We'll call it popup.css. This is just for decoration of the page, we'll put it in the same folder as the popup.html file.
To install the add-on we created, we are going to load it temporarily. Let's start by opening the Add-ons Manager:
This will open up the Add-ons Manager, make sure "Extensions" is selected on the left-hand side and click the gear to select "Debug Add-ons".
Click on the "Load Temporary Add-on..." button:
Select the manifest.json file from within our hello-world project folder:
This should install the add-on for this session only:
Our extension will print messages to the error console using console.log(), so we need to open the error console first, in order to see those log entries. Hit the "Inspect" button under the add-on's listing (pictured above), this will open the Developer Tools window.
Make sure the "Console" tab is selected in the Developer Tools. Click the "Persist Logs" checkbox in the top right-hand corner of the Developer Tools window so that we can see the output from the add-on after we've interacted with it (otherwise, it only shows output as it is happening).
Now we can give our new add-on a whirl. Head to the home tab and find the new "Hello World" button in the main toolbar in the top right-hand corner. Click on it to see a popup with the Hello, World! message.
Now, if you look at the Developer Tools window, you should see something like the following in the console:
Once the add-on is ready for release or if you want to share it with others, you need to create a single add-on file. Simply zip the content of the add-on's project folder and use the xpi file extension. That file can be installed from the gear menu in the Thunderbird Add-ons Manager.
You can grab the icons we use for this example from the . Make sure to create an images directory in the hello-world project folder for them.
The allowed keys for the browser_action button are described in our . We define a popup HTML page, which should be loaded if the button is clicked, a title and an icon.
The default disallows JavaScript placed directly in <script> tags and inline event handlers like onclick. Place all JavaScript code into a separate file (like popup.js in this example) and use instead of inline event handlers.
First, let's double-check that we created and have them in the right places:
