Implement a settings page

A settings page gives users a way to see and change settings (sometimes also called "preferences" or "options") for the extension.

With WebExtension APIs, settings are generally stored using the storage API. Implementing a settings page is a three-step process:

  • Write an HTML file that displays settings and lets the user change them.
  • Write a script, included from the HTML file, that populates the settings page from storage and updates stored settings when the user changes them.
  • Set the path to the HTML file as the options_ui key in manifest.json. By doing this, the HTML document will be shown in the browser's add-on manager, alongside the extension's name and description.

Note: You can also open this page programmatically using the runtime.openOptionsPage() function.

A simple extension

First, we'll write an extension that adds a blue border to every page the user visits.

Create a new directory called settings, then create a file called manifest.json inside it with the following contents:

json
{
  "manifest_version": 2,
  "name": "Settings example",
  "version": "1.0",

  "content_scripts": [
    {
      "matches": [""],
      "js": ["borderify.js"]
    }
  ]
}

This extension instructs the browser to load a content script called "borderify.js" into all web pages the user visits.

Next, create a file called borderify.js inside the settings directory, and give it these contents:

js
document.body.style.border = "10px solid blue";

This just adds a blue border to the page.

Now install and test the extension.

Adding settings

Now let's create a settings page to allow the user to set the color of the border.

First, update manifest.json so it has these contents:

json
{
  "manifest_version": 2,
  "name": "Settings example",
  "version": "1.0",

  "content_scripts": [
    {
      "matches": [""],
      "js": ["borderify.js"]
    }
  ],

  "options_ui": {
    "page": "options.html"
  },

  "permissions": ["storage"],

  "browser_specific_settings": {
    "gecko": {
      "id": "[email protected]"
    }
  }
}

We've added three new manifest keys:

options_ui

This sets an HTML document to be the settings page (also called options page) for this extension.

permissions

We'll use the storage API to store the settings, and we need to ask permission to use this API.

browser_specific_settings

You have to include an extension id in order to save and retrieve settings from synchronized storage.

Next, because we've promised to provide options.html, let's create it. Create a file with that name inside the settings directory, and give it the following contents:

html


  
    
  

  
    

This defines a

with a labeled text and a submit

Learn more