Google Chrome
Hit F12 or CTRL + SHIFT + J to open browser console.
Click the opened console, then hit CTRL + SHIFT + P, or...
Click the vertical three dots on top far right on the console, then click Run command.
Then type in capture or screenshot. Pick (click) the Capture full size screenshot.
You need to provide where to keep the screenshot. It will be an image with .png type (usually). And BAM!
A full grown screenshot is saved.I mean full page screenshot.
Microsoft Edge
Almost similar to the above steps. But Edge has different shapes for the icons. Instead of vertical three dots, Edge has the horizontal three dots. Same location, top far right of the browser console.
The rest of the steps are similar.
And BAM!
ℹ️ Limitation
Content Served With Iframe
For website which implements iframe for Content Security Policy (CSP) Enforcement (or sandboxing), for instance, Blogger — the preview page, and many other sites — especially with login (user management), this full size screenshot feature won't capture the entire page. Especially when the iframe is
scrollable.
The reason is that the "entire page" you see is actually embedded within an iframe, which is served as a separate document. The full page capture feature in Chrome or Edge only grabs the parent HTML document, from top to bottom, and does not include the full (scrollable) content of the embedded iframe. But it still includes the partial, viewable content of the iframe.
Content Served With Scrollable Container
The other limitation is for a webpage which implements overflow-y: auto or overflow-y: scroll to specific containers inside the page, and the document.body of the HTML is set to have overflow-y: none (no scrollbar).
Screenshot or full-page capture tools, they often only capture the main viewport (document.body). If the content is set as above technique (placed inside a scrollable container), it won't be captured fully unless scrolled manually.
Mozilla Firefox
Chrome and Edge use the Chromium engine, which has a well-supported headless mode and full-page rendering capability. Firefox, well, not quite. Use Chrome or Edge for consistent full-page captures — especially when dealing with dynamic layouts or needing automation. Firefox is serviceable for static, clean pages but unreliable for anything complex.




Comments
Post a Comment