Screenshot is transparent and it doesn't capture correctly the page

[matheusgontijo]

The extension was was working perfectly few weeks ago, but I'm not sure what happened that it stopped working.

When I click on the button for taking the full page screenshot:

1. it goes to the bottom of page (as normal)
2. it starts taking screenshots from bottom top, and then scrolling up (as normal)
3. it opens a new tab in order to display the result (as normal)
4. >>> error comes here. it display a transparent image... and not the correct print of the page I requested. Even if I download it is a transparent PNG

I attached a screenshot with the result I just described.

System:

• Fedora 27 - 64 bits
• Chrome Version 65.0.3325.181 (Official Build) (64-bit)

And here are the extensions I use, if it helps to find out a possible extension conflict.

If you need any extra information, please let me know and I'll describe as soon as possible.

Thanks for helping. I love this extension.

[mrcoles]

Hi @matheusgontijo thank you for sharing! This appears to be a bug in Chrome itself, and it’s currently slated to be fixed in release v67. https://bugs.chromium.org/p/chromium/issues/detail?id=831773

Are you able to test running chrome with the --disable-gpu flag and seeing if it works?

[matheusgontijo]

Hey @mrcoles using --disable-gpu works!

It has nothing to do with the extension itself. Thanks for the heads up though!

Well, let's watch closely if they fix the issue soon... I hope in the up coming weeks.

[mrcoles]

Thanks for checking! I’ll leave this open until the issue is resolved in Chrome.

[thecjharries]

Thanks @matheusgontijo and @mrcoles. I have the exact same issue on the same platform with the same version. I turned to this extension because it's what I used before DevTools added the functionality. I really appreciate the discussion. I've listed a few alternatives below that can be used in the interim.

If you don't mind running multiple browsers in tandem, Firefox supports full pages as well.

If you're on a different flavor of Linux, Shutter used to be the generally recommended solution. Unfortunately its dependencies are woefully out of date and anything not Ubuntu might not be great (e.g. it's iffy in Fedora 26 and the underlying library, webkitgtk3, needs things that don't exist in Fedora 27).

In some cases you can get away with printing to a PDF. You might have to alter the CSS yourself (especially if it's got distinct print styling) and even then there could be some issues. Of course you'll also have to convert the PDF to whatever format you wanted.

If, like me, you're trying to easily capture the contents of a lengthy, session-dependent iframe driving the page in Chrome 65 on Fedora 27, you are probably SOL. A decent, if time-consuming and not very fun, option is programmatically scrolling the window and taking screenshots to be stitched together later. For example, using xdotool with ImageMagick, something like this could work:

#!/bin/bash

# Note: I haven't tested this verbatim and my memory is a little fuzzy in places.
# Use with an ounce or two of caution.
# If I do actually go through with a CLI solution I'll update this answer.

WID=`xdotool search 'Google Chrome'`

# Alternatively, if that provides too many results,
#     xdotool search --name '<something in the tab title>'
# or
#     xdotool search --name '<something in the tab title>.*Google Chrome'
# (it supports regex)

# Manually, 
#     xdotool selectwindow
# will give you a pointer to find the window you want.

xdotool windowactivate --sync $WID

# the loop was chosen at random; do something that works for you
for loop_index in $(seq 1 10); do
    # take the screenshot
    import -window "$WID" "/output/file/path_${loop_index}.png"
    # scroll the page
    xdotool key --clearmodifiers space
    # or whatever you want to use to scroll; note Page Up/Down can be weird
done

A good list of other screenshot tools, as well as good code examples, can be found on Arch Wiki.

Once again, thanks @matheusgontijo for putting together a great issue and @mrcoles for an in-depth response. Hopefully no one else runs into my situation.