How to write an Experiment¶
An experiment comprises at least three files:
- api.js: Your code to implement the API.
- schema.json: Defines the API - types, methods, etc.
- install.rdf: Install manifest.
The namespace is the value used in the API such as “login” or “media”. This is what developers will use in the API, such as “browser.login” or “browser.media”. The namespace needs to be consistent in all places of the extension:
- api.js: ExtensionAPI.getAPI() must return an object with a single top-level property: “namespace”.
- schema.json: the permissions must be “namespace”.
- install.rdf: the id must be “email@example.com”.
You can see an example of all this in the boilerplate example where the namespace is “boilerplate”.
Using the boilerplate¶
The boilerplate example provides a simple example that you can download and use in whatever way you see fit.
To get the boilerplate example on Linux or OS X, run the following command:
curl -L https://github.com/web-ext-experiments/boilerplate-experiment/archive/master.tar.gz | tar zxf -
You will then be able to change the example to meet your needs.
Designing your API¶
Installing the experiment¶
Your experiment can be installed like any other add-on, for example:
- You can zip an .xpi, and then install it from about:addons > Install Add-on From File.
zip experiment.xpi api.js install.rdf schema.json
- You can load the install.rdf temporarily from about:debugging > Load Temporary Add-on.
Using the experiment¶
Once you have experiment installed, you can then create a WebExtension using the API provided in the experiment. The only requirement is to add into the manifest of the WebExtension the permission for the experiment.
For example from logins:
This gives you permission to use the API. But the API might require more permissions, for example to actually use the logins API for all urls, you’ll need to do the following:
"permissions": ["experiments.logins", "logins", "<all_urls>"]
Please see the documentation for each experiment to find what permissions you need.