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.

注意: You can also open this page programmatically using the runtime.openOptionsPage() 函数。

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:

{
  "manifest_version": 2,
  "name": "Settings example",
  "version": "1.0",
  "content_scripts": [
    {
      "matches": ["<all_urls>"],
      "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:

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

					

This just adds a blue border to the page.

现在 安装 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:

{
  "manifest_version": 2,
  "name": "Settings example",
  "version": "1.0",
  "content_scripts": [
    {
      "matches": ["<all_urls>"],
      "js": ["borderify.js"]
    }
  ],
  "options_ui": {
    "page": "options.html"
  },
  "permissions": ["storage"],
  "browser_specific_settings": {
    "gecko": {
      "id": "addon@example.com"
    }
  }
}

					

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:

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
  </head>
  <body>
    <form>
        <label>Border color<input type="text" id="color" ></label>
        <button type="submit">Save</button>
    </form>
    <script src="options.js"></script>
  </body>
</html>

					

This defines a <form> with a labeled text <input> and a submit <button> . It also includes a script called options.js .

创建 options.js , again in the settings directory, and give it the following contents:

function saveOptions(e) {
  e.preventDefault();
  browser.storage.sync.set({
    color: document.querySelector("#color").value
  });
}
function restoreOptions() {
  function setCurrentChoice(result) {
    document.querySelector("#color").value = result.color || "blue";
  }
  function onError(error) {
    console.log(`Error: ${error}`);
  }
  let getting = browser.storage.sync.get("color");
  getting.then(setCurrentChoice, onError);
}
document.addEventListener("DOMContentLoaded", restoreOptions);
document.querySelector("form").addEventListener("submit", saveOptions);

					

This does two things:

  • When the document has loaded, it fetches the value of "color" from storage using storage.sync.get() . If the value isn't set, it uses the default "blue" . This retrieves the values from the sync storage area.
  • When the user submits the form by clicking Save, it stores the value of the textbox using storage.sync.set() . This saves the value to the sync storage area.

注意: Specifying a separate .js file is required. You cannot use inline JavaScript.

You could store the settings values in local storage instead if you feel that local storage is preferable for your extension.

注意: 实现为 storage.sync in Firefox relies on the Add-on ID. If you use storage.sync , you must set an ID for your extension using the browser_specific_settings  key in manifest.json , as shown in the example manifest above. See bug 1323228 for related information.

Finally, update borderify.js to read the border color from storage:

 function onError(error) {
  console.log(`Error: ${error}`);
}
function onGot(item) {
  let color = "blue";
  if (item.color) {
    color = item.color;
  }
  document.body.style.border = "10px solid " + color;
}
let getting = browser.storage.sync.get("color");
getting.then(onGot, onError);

					

At this point, the complete extension should look like this:

settings/
    borderify.js
    manifest.json
    options.html
    options.js
					

Now:

  • reload the extension
  • load a web page
  • visit " about:addons " to open the settings and click the Preferences button next to the extension's entry and change the border color.
  • reload the web page to see the difference.

了解更多

Found a problem with this page?

最后修改: , 由 MDN 贡献者

  1. 浏览器扩展名
  2. 快速入门
    1. What are extensions?
    2. Your first extension
    3. Your second extension
    4. Anatomy of an extension
    5. Example extensions
    6. What next?
  3. 概念
    1. Using the JavaScript APIs
    2. Content scripts
    3. Match patterns
    4. Working with files
    5. 国际化
    6. Content Security Policy
    7. Native messaging
    8. Differences between API implementations
    9. Chrome incompatibilities
  4. 用户界面
    1. 用户界面
    2. Toolbar button
    3. Address bar button
    4. Sidebars
    5. Context menu items
    6. Options page
    7. Extension pages
    8. Notifications
    9. Address bar suggestions
    10. Developer tools panels
  5. 如何
    1. Intercept HTTP requests
    2. Modify a web page
    3. Insert external content
    4. Share objects with page scripts
    5. Add a button to the toolbar
    6. Implement a settings page
    7. Work with the Tabs API
    8. Work with the Bookmarks API
    9. Work with the Cookies API
    10. Work with contextual identities
    11. Interact with the clipboard
    12. Build a cross-browser extension
  6. Firefox differentiators
  7. JavaScript API
    1. Browser support for JavaScript APIs
    2. alarms
    3. bookmarks
    4. browserAction
    5. browserSettings
    6. browsingData
    7. captivePortal
    8. clipboard
    9. 命令
    10. contentScripts
    11. contextualIdentities
    12. Cookie
    13. devtools
    14. dns
    15. downloads
    16. events
    17. extension
    18. extensionTypes
    19. find
    20. history
    21. i18n
    22. identity
    23. idle
    24. management
    25. menus
    26. notifications
    27. omnibox
    28. pageAction
    29. permissions
    30. pkcs11
    31. privacy
    32. proxy
    33. runtime
    34. search
    35. sessions
    36. sidebarAction
    37. storage
    38. tabs
    39. theme
    40. topSites
    41. 类型
    42. userScripts
    43. webNavigation
    44. webRequest
    45. windows
  8. Manifest keys
    1. 介绍
    1. 作者
    2. background
    3. browser_action
    4. browser_specific_settings
    5. chrome_settings_overrides
    6. chrome_url_overrides
    7. 命令
    8. content_scripts
    9. content_security_policy
    10. default_locale
    11. description
    12. developer
    13. devtools_page
    14. dictionaries
    15. externally_connectable
    16. homepage_url
    17. icons
    18. incognito
    19. manifest_version
    20. name
    21. offline_enabled
    22. omnibox
    23. optional_permissions
    24. options_page
    25. options_ui
    26. page_action
    27. permissions
    28. protocol_handlers
    29. short_name
    30. sidebar_action
    31. storage
    32. theme
    33. theme_experiment
    34. user_scripts
    35. version
    36. version_name
    37. web_accessible_resources
  9. Extension Workshop
    1. Develop
    2. Publish
    3. Manage
    4. Enterprise
  10. Contact us
  11. Channels
    1. Add-ons blog
    2. Add-ons forum
    3. Add-ons chat