enter about:addons in the URL bar, to open Add-ons Manager.To debug options pages, use the Toolbox Debugger in the split console view so you can view the Console below Debugger. Options pages display in an iframe in Add-ons Manager. You use an options page to enable the user to set and save options and settings that affect the behavior of your extension. This example is in the webextensions-examples repository.Īn options pages is an HTML page shown when the user accesses your extension's preferences in Add-ons Manager, either by opening Add-ons Manager themselves or using a link provided in your extension. We use the favourite-colour extension example to illustrate the debugging features relevant to options pages. In the Debugger you can set breakpoints, step through code, modify the extension's state, and do everything else you'd expect to be able to do in a debugger.įor more information about using the debugger, see the Debugger guide.
For example, you can call the notify() function: Using the Console command line, you can access and modify the objects created by your background scripts. Note that the console shows all errors raised by the browser, not just errors related to your extension's code.įor example, the notify-link-clicks-i18n example extension logs a message from its background script when it receives a message from one of its content scripts. To get started, open your background script in Sources.Īs you run your extension, the Console displays logged output, including calls to console.log() made by the extension's background scripts and any errors the browser raises as it executes these scripts. To debug background scripts, use the Toolbox Debugger in the split console view so you can view the Console below Debugger. Background scripts are loaded inside an invisible background page: by default, this is an empty HTML document, but you can specify a custom page and define it as the background page using the manifest.json background key. These scripts remain loaded for the lifetime of the extension. This example is in the webextensions-examples repository.īackground scripts enable an extension to maintain a long-term state or perform long-term operations, independently of any web page or browser window. We use the notify-link-clicks-i18n extension example to illustrate the debugging features relevant to background scripts. It occasionally contains more detailed information about errors reported to your extension. This console contains messages from the whole browser, including your and other extensions. Log messages not associated with an extension script, such as the stderr output of the nativeMessaging APIĬan only be viewed via the Browser Console. Log messages from content scripts can be viewed in the developer tools of the tab where the content script runs instead of about:debugging, see: The Developer tools toolbox at about:debugging shows log messages from extension scripts. Log messages can usually be viewed via the Console of the context where the script runs. with the Console API or by triggering (uncaught) errors. Your extension can generate log messages, e.g. You can now drag the toolbox tab to a separate window, so you can place it alongside the window where you're executing the extension. You do this using the split console, press esc to activate this mode. There is an overview of all relevant places to look for messages at Viewing log output.įor much of the debugging work, it's useful to be able to view Console with Inspector or Debugger. This console shows messages from your background script and extension pages other logs may appear elsewhere.
Use plain language in any privacy policy or license agreement.Select the right platforms and versions.The add-on description can be longer, but not too long.Focus on key features in your screenshots.
Make sure your summary is just long enough.