Firefox 63, how to save screenshot of full webpage

[darkoshi]

Firefox used to let you save a screenshot of the full web-page via the Developer Toolbar:
https://darkoshi.dreamwidth.org/629515.html

(By the way, if you accidentally tried that from the toolbar shown in the Web Console instead of the Developer Toolbar, it didn't work, and showed an error, "SyntaxError: missing ; before statement".)

The Developer Toolbar has been removed in version 63 of Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=gcli-removal
https://www.ghacks.net/2018/05/21/firefox-62-developer-toolbar-removal/

So now you can save a screenshot from the Web Console; but you need to include a colon (:) in front of the command:
:screenshot --clipboard --fullpage

See:
https://www.ghacks.net/2018/08/27/screenshots-from-the-firefox-developer-tools-console/

In the Web Console settings, you can also select the "Take a screenshot of the entire page" option under "Available Toolbox buttons", to get a Web Console toolbar button for taking a screenshot. Using that button, rather than saving the screenshot to the clipboard, automatically saves a PNG image in the Downloads folder.

Comments

[darkoshi]

Only the thing that was called "Developer Toolbar" is gone. At the other Web Developer tools are still there, as far as I know. I only ever used the Developer Toolbar for taking full-page screenshots, not for anything else.
But typing help (in an old FF version) in it shows that all these commands were available:

GCLI is an experiment to create a highly usable command line for web developers.

Available Commands:
addon - Manipulate add-ons help addon
appcache - Application cache utilities help appcache
break - Manage breakpoints help break
calllog - Commands to manipulate function call logging help calllog
clear - Clear the output area help clear
console - Commands to control the console help console
context - Concentrate on a group of commands help context
cookie - Display and alter cookies help cookie
dbg - Manage debugger help dbg
edit - Tweak a page resource help edit
export - Export resources help export
eyedropper - Grab a color from the page help eyedropper
folder - Open folders help folder
help - Get help on the available commands help help
highlight - Highlight nodes help highlight
inject - Inject common libraries into the page help inject
inspect - Inspect a node help inspect
jsb - JavaScript beautifier help jsb
listen - Open a remote debug port help listen
mdn - Retrieve documentation from MDN help mdn
measure - Measure a portion of the page help measure
media - CSS media type emulation help media
pagemod - Make page changes help pagemod
paintflashing - Highlight painted area help paintflashing
pref - Commands to control settings help pref
qsa - Perform querySelectorAll on the current document and return number of matches help qsa
resize - Control Responsive Design Mode help resize
restart - Restart Firefox help restart
rulers - Toggle rulers for the page help rulers
screenshot - Save an image of the page help screenshot
security - Display supported security and privacy features help security
unhighlight - Unhighlight all nodes help unhighlight
unlisten - Close all remote debug ports help unlisten

[marahmarie]

I honest to whatever cannot believe they'd leave the command line tool (we used to have an add-on for that that was a collaboration between a non-Moz dev and Moz starting 10 years ago; it was so unpopular Mozilla eventually yanked it) and pull the toolbar. I don't think they always make the wisest decisions. Considering how much the user base is shrinking I really can't see why they don't do in-browser polling before they pull something, anything, at this point (if they'd done that starting a while ago they'd still have the status bar, for sure).

[marahmarie]

It doesn't make sense, either, because in the bug to yank the toolbar they gripe about GCLI being neglected/not kept up and in the next breath tada here's a command line tool based on GCLI folks, enjoy I just gah Mozilla *flails*...oh I see, that was in old version, not the new (I just looked high and low through the Beta and googled but yeah, that end of it seems gone now, too).

Shift + f2 still brings it up in Waterfox (don't know if that's what you're using when you say "old FF" version).

[darkoshi]

By old FF, I meant Firefox Portable 52.9esr which I still have for testing/comparison purposes like this.

I currently use Waterfox as my main browser, but yesterday I was using FF 63 (because I use it for certain things). That's how I found out that the Developer Toolbar was gone. Actually, after the screenshot command wasn't working for me in FF 63 (I was typing it in the Web Console but without : in front), I tried it in Waterfox, and couldn't get it to work there either (because I was using the Web Console by mistake, instead of the Dev Toolbar). Then when I finally figured out my mistake in Waterfox, I went back to FF 63, and was like "Where did the Dev Toolbar go?!"

[marahmarie]

Oh wow, OK, thanks for the clarification...and way to go, Mozilla *rolls eyes*

They could've hired a dev to upkeep GCLI/the toolbar. Just hired them part-time to maintain it if they were so concerned about bitrot/lack of maintenance on it/lack of updated code. I haven't used the internal command line for Fx since the add-on existed that I was talking about (it was kind of neat, I could just never remember to use it often enough before eventually it sort of morphed into something I didn't like so much, with too much GUI and not enough commands, before they killed it off altogether).