Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

What is difference between (Inspector > Console) v.s. (Tools > Developer Toolbar)

  • 3 replies
  • 1 has this problem
  • 13 views
  • Last reply by cor-el

Just am curious what the difference is here between the two and the available functionality.. For example, i just discovered the "Developer Toolbar" has some wonderful 'screenshot' functionality built in..


Follow up questions,


Is there any way to communicate with the browser (using selenium maybe?) to execute these 'savescreenshot' functions? (along with passing parameters, like URL, etc? )

Can you enlighten me on how the browser is taking fullpage screenshots? (inclusive of y-overflow)

Just am curious what the difference is here between the two and the available functionality.. For example, i just discovered the "Developer Toolbar" has some wonderful 'screenshot' functionality built in.. Follow up questions, Is there any way to communicate with the browser (using selenium maybe?) to execute these 'savescreenshot' functions? (along with passing parameters, like URL, etc? ) Can you enlighten me on how the browser is taking fullpage screenshots? (inclusive of y-overflow)

Chosen solution

Both use the built-in API to take a screenshot, so there is no difference.

Note that Firefox has a setting in the developer toolbox settings to add a button to the toolbar of the Web Developer toolbox that you can open via Inspect Element (right-click context menu) to take a full page screenshot.

You can type a space and two dashes (--) to see all options and use the cursor Up and Down keys to cycle through available options.

A full page screenshot includes all data that you see on the web page including data that you can find by scrolling the page horizontally or vertically, but obviously not data that is hidden.

I'm not using Selenium, so I don't know if it is possible the execute commands like that or paste data in the command line of the Developer toolbar.

I assume that iMacros should be able to do this, but I haven't used this extension as well.

Read this answer in context 👍 0

All Replies (3)

Chosen Solution

Both use the built-in API to take a screenshot, so there is no difference.

Note that Firefox has a setting in the developer toolbox settings to add a button to the toolbar of the Web Developer toolbox that you can open via Inspect Element (right-click context menu) to take a full page screenshot.

You can type a space and two dashes (--) to see all options and use the cursor Up and Down keys to cycle through available options.

A full page screenshot includes all data that you see on the web page including data that you can find by scrolling the page horizontally or vertically, but obviously not data that is hidden.

I'm not using Selenium, so I don't know if it is possible the execute commands like that or paste data in the command line of the Developer toolbar.

I assume that iMacros should be able to do this, but I haven't used this extension as well.

Modified by cor-el

thank you cor-el for you time and reply.

Your response is helpful, but I was truly looking to for a way to automate this with selenium.

For anyone else interested..

I was looking to take fullpage screenshots of a website -- while still being able to manipulate the DOM

- there are tools like 'phantomJS' that take fullpage screenshots but I do not believe you have ability to touch the html

- I was previously using 'nightwatchJS' ontop of selenium, also leveraging 'chrome-driver' because i had issues with never versions of FF. This only supports 'viewport' screenshots

The answer for me was to: - revert back to older version of FF (im using 42.0) - convert my nightwatch scripts back to firefox supported syntax.

Fullpage screenshots with the ability to manipulate DOM and while maintaining my test suite.

Modified by chris_millah