![]() 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. Storage to view details of data stored by the extension.Debugger to set breakpoints and watchpoints in your extension's JavaScript, and examine and modify the extension's state.It also provides a command line, where you can execute JavaScript in the extension's context. Console to view messages logged by the extension and error messages logged by the browser as it runs the extension.Inspector to examine and modify the HTML and CSS used to build your extension's pages.in the left-hand menu, click This Firefox (or This Nightly).Ī new tab opens showing Inspector in the Toolbox.You use an implementation of the developer tools called Toolbox to debug extensions. Removing your extension from distribution.Will I ever be able to sell through AMO?.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. ![]()
0 Comments
Leave a Reply. |