Issue metadata
Sign in to add a comment
|
[devtools] full-page screenshot did not capture the entire page
Reported by
kaycebas...@gmail.com,
Jun 23 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3138.0 Safari/537.36 Steps to reproduce the problem: 1. capture a full-page screenshot of https://css-tricks.com/introduction-webpack-entry-output-loaders-plugins/ What is the expected behavior? Everything on the page, down to the footer, is captured in the screenshot What went wrong? The screenshot is cut-off at the "Plugins" section Did this work before? N/A Chrome version: 61.0.3138.0 Channel: canary OS Version: OS X 10.12.5 Flash Version:
,
Jun 26 2017
In my experience the tool captures everything initially visible to the user, but doesn't capture any of the screen "below the fold." Version 59.0.3071.115 (Official Build) (64-bit) OS Version: OSX 10.11.6
,
Jun 26 2017
Chrome cuts the screenshots at 16384 pixel height, simple as that. The PNG spec [1] allows image height of up to 4,294,967,295 so it's a bug in Chrome or in whatever library it uses. [1]: http://www.libpng.org/pub/png/spec/iso/index-object.html#11IHDR
,
Jun 26 2017
Duplicate of issue 719334: >This is an implementation limitation deep inside Chrome. I doubt we are going to change that, but I'll leave this bug around in case something changes. See also issue 638281 : >The 16384px limit stems from the maximum texture size used by the compositor. For GL rendering, this is actually read from the GL context, so a limitation of the GL backend (GPU, software GL, etc.) that can't be changed. For the software GL backend we use with headless, this limit is 16384px. If you're using pure software rendering (without GL support), chromium currently sets the max texture size to 16384px, too. You could change that constant in the implementation to something larger, and run with --disable-gpu to force software rending (I tried this, it does seem to work). But note that software rendering doesn't support WebGL content (and probably also any CSS that requires GL to render correctly). ========== Not even showing a warning that the screenshot is cut off is a really bad UX.
,
Jun 27 2017
As per comment #4 marking it as duplicate for issue 719334, please undo it if anybody feel so Thank You... |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Jun 23 2017Labels: Needs-Triage-M61 Needs-Bisect