To debug background scripts, use the Toolbox Debugger in the split console view so you can view the Console below Debugger. Non-persistent background scripts are recommended because they consume less of the browser's resources.īackground 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. In contrast, non-persistent background scripts load when needed to respond to an event and unloaded when they become idle. ![]() Persistent background scripts remain loaded for the lifetime of the extension. ![]() These scripts can be persistent or non-persistent. This example is in the webextensions-examples repository.īackground scripts enable an extension to monitor and react to events in the browser, such as navigating to a new page, removing a bookmark, or closing a tab. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |