I have developed an add-on for Firefox and Chrome. It has content scripts. I want to access them in the browser tab's console (on Firefox the Web Console). For example, I want to enter a global variable defined in the content script(s) in the console, and it will output its value.
In Chrome, I can open the console by pressing F12, then navigate to the Console tab in the developer tools. It has a dropbox, right after the filter button, to select which context I am in (page/content script):
In Firefox, how to do the same thing?
I have developed an add-on for Firefox and Chrome. It has content scripts. I want to access them in the browser tab's console (on Firefox the Web Console). For example, I want to enter a global variable defined in the content script(s) in the console, and it will output its value.
In Chrome, I can open the console by pressing F12, then navigate to the Console tab in the developer tools. It has a dropbox, right after the filter button, to select which context I am in (page/content script):
In Firefox, how to do the same thing?
Share Improve this question edited Dec 31, 2019 at 0:02 Makyen♦ 33.3k12 gold badges92 silver badges125 bronze badges asked Mar 3, 2017 at 6:01 zhmzhm 3,6414 gold badges37 silver badges56 bronze badges 6- Please define what you mean by "access to them" (e.g. do you mean view in debugger (just switch to the debugging tab)?, enter JavaScript into the Console in that context?, or something else?). Please keep in mind that what you are calling the browser console is actually the Web Console. The Browser Console (Ctrl-Shift-J, or Cmd-Shift-J on OSX) has a specific meaning for Firefox. There are various consoles in Firefox and Chrome, which each have their appropriate uses. – Makyen ♦ Commented Mar 3, 2017 at 6:34
- @Makyen By access, I mean for example, I can enter a global variable defined in content scripts in console, and it will output its value. – zhm Commented Mar 3, 2017 at 6:39
- Is viewing the variable's value in the debugger sufficient? You can do that by selecting the code file in the Debugger tab. To be more explicit: Is what you need something that can only be handled by being able to enter lines of code in a console and have them execute within the content script's context/scope? – Makyen ♦ Commented Mar 3, 2017 at 6:54
- @Makyen My extension doesn't work well for iframes. Firstly I want to make sure, if iframes have loaded my content scripts (by checking if global variables exist in content script console). View variables in debugger can be ambiguous, because I don't know where I am (Am I in page? Or am I in iframe?) – zhm Commented Mar 3, 2017 at 6:58
- I don't see a good solution for exactly what you want (you should submit a bug/RFE in bugzilla. I'm still not sure exactly what you're really trying to do, other then that it is differentiating values between the main frame/iframe. From your description, I might try setting info in the DOM using Element.dataset. These are then quite easily visible in the DOM Inspector. – Makyen ♦ Commented Mar 3, 2017 at 8:16
4 Answers
Reset to default 8The ability to do this doesn't exist
The ability to change the context/scope of the Web Console to that of the an extension's content scripts does not exist. In addition, this capability does not exist in any of the other ways to view a console in Firefox. A bug/RFE is filed on Bugzilla requesting this functionality, with an overall tracking bug for the feature.
You can change the console's context/scope to an iframe's page scripts
You can change the console into the context/scope of the iframe's page scripts by selecting the frame from the drop-down menu opened from the frame-selector drop-down:
If this drop-down icon is not appearing for you, go to the DevTools settings and check "Select an iframe as the currently targeted document". However, doing this:
- does not switch into the content script context/scope, and
- may not work properly with the JavaScript Debugger, but this may have been improved since this answer was written in 2017.
JavaScript Debugger
You can use the JavaScript Debugger with WebExtensions content scripts. The content scripts for the extension are listed in the "Sources" section under the name of the extension, then the filename of the content script. You can view the content of variables, set breakpoints, etc. However, this does not give you the ability to explicitly switch to the context of a child frame. Placing debugger;
directives in the JavaScript which is running in the child iframe's content script is ineffective at getting the console context to change to the content script context.
JavaScript Debugger debugging content script (in top frame) [This screenshot is quite old. While the current general layout is the same, there have been significant improvements.]:
Console in background script context
If you were wanting to open a console which was in the context of your WebExtensions' background script, you could do so by navigating to "about:debugging", clicking to use "This Firefox" for debugging extensions and service workers, then clicking on the "Inspect" button for the extension you are interested in debugging. However, this will not get you access to a console in the content script's context.
Workarounds for seeing variable values in the iframe
For what you need: unambiguously indicating that values are in the iframe context, not the top frame; I see two methods of doing so:
Use
console.log()
with information prepended that clearly indicates that the script believes it is running in the iframe. For example:console.log('In iframe', 'foo=', foo);
So that you don't have to have
'In iframe'
in every call toconsole.log()
you make, you could create a function that prepends that text to all calls to that function. You could even override theconsole.log()
function so your code still just callsconsole.log()
.However, this only tells you that your code thinks that it is running in the iframe. Part of what you may be debugging is your content script code detecting that it is in an iframe.
This method does not indicate with certainty that the reported values are actually in the iframe.
Store values into the DOM using Element.dataset, or other DOM element attributes, and then inspect the DOM for these values. You can then use the Page Inspector to view these attributes.
This method can be used to unambiguously show that the values are ones in the iframe, and exactly which iframe, without relying on the code running in the iframe to accurately determine that it is in an iframe and which iframe it is in.
A simple solution is to just console.log()
in the content script and then click the sourcemap link to view the script. As shown below:
It's not yet possible. There is a bug Implement UI for switching context to content script opened (since Nov 2017) for that.
In Firefox Developer Edition, go on "about:debugging" page and click on the "Debug" button beside your add-on to open the dev tools.