Allow screenshots larger than 16384px tall |
|||
Issue descriptionThis is a known issue, but afaik has no tracking bug. Most relevant discussion: https://groups.google.com/a/chromium.org/d/topic/headless-dev/DqaAEXyzvR0/discussion > The 16384px limit stems from the maximum texture size used by the compositor. For GL rendering, this is actually read from the GL context (https://cs.chromium.org/chromium/src/cc/resources/resource_provider.cc?q=f:resource_provider.cc+%22GL_MAX_TEXTURE_SIZE,+%26max_texture_size%22), 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. (https://cs.chromium.org/chromium/src/cc/resources/resource_provider.cc?q=f:resource_provider.cc+%22max_texture_size+%3D+%22) 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).
,
Oct 2 2017
,
Dec 18 2017
If this is resolved, it will be great as currently we have to stitch multiple images to get the whole image. Hope this will be resolved soon.
,
Jan 1 2018
Yup, we have to stitch screenshots too. It's not super tricky, but it's not great that we're all separately implementing the same feature.
,
Jan 2 2018
FWIW here's a puppeteer script that will capture multiple images from a tall page: https://github.com/GoogleChrome/puppeteer/blob/230be28b067b521f0577206899db01f0ca7fc0d2/examples/screenshots-longpage.js It won't stitch them together, but https://github.com/lovell/sharp or other image libraries can help with that.
,
Jan 3
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||
►
Sign in to add a comment |
|||
Comment 1 by paulir...@chromium.org
, Oct 2 2017