This is what you want when debugging a webpage, but not an add-on's background scripts. You, probably, are looking at the Web Console (keyboard shortcut F12) which is associated with only a single tab.
This console will display only content from the WebExtension which you are inspecting. You can then click on the Console tab within that browser tab. This will open a new tab with the debugger. You can access the Add-on Debugger though about:debugging➞Inspect (use the "Inspect" button that's associated with the WebExtension you are debugging there's a separate button for each extension). This includes background scripts, scripts running in popups, options pages, and any other page loaded from the extension as the main URL for a tab, or iframe. This is what you should be using to view console output from scripts running in the background context of your WebExtension. However, complex data will not be available (e.g. The console in this toolbox will show output from both scripts running in the background context and from content scripts. If it is not available you can enable it through options from the Web Console settings page.
You can access it from Tools➜Web Developer➜Browser Toolbox (keyboard shortcut Ctrl- Alt- Shift- I On a Mac: Cmd- Alt- Shift- I). If you have it enabled, you could also use the Browser Toolbox console.
In older versions of Firefox, this was the console to use to see output from extensions. You can access the Browser Console from Tools➜Web Developer➜Browser Console (keyboard shortcut Ctrl- Shift- J, or Cmd- Shift- J on Mac). Depending on what you are doing, the Browser Console may show output from a WebExtensions Experiment. You can have it show output from all WebExtensions by selecting to display "Show Content Messages", which is available from the popup that opens when you click on the gear-like symbol "⚙️" in the upper right of the window, just to the right of "Requests". The Browser Console no longer shows output from WebExtensions background pages by default. Mozilla describes what extension output can be seen in which console in their Debugging article. If you are not seeing it, then you are, probably, looking at the wrong console. You can change the setting `` in `about:config` if you want even those to be opened right next to the current.Your code is correct as written, it works and outputs to console. Tabs that are opened by clicking on links are opened at the default location. You need to do that manually on the extension page in settings. Keyboard shortcuts are not automatically set up. You can use `Ctrl-Y` (`Ctrl-Shift-Y` on Windows) to open a new tab at the default location. Tabs that are being re-opened are thus not included. Open tabs that would normally be opened last next to the current one. Open new tabs to the right of the current one.
0 kommentar(er)
