Does this still work for full page screenshots? Every-time I use the extension it snaps the first frame and shows it in the top right corner of screen and doesn't try to scroll or anything?

Hi there, I use Blipshot a lot for work and it's suddenly not taking the whole page, just the visible. I see a thread about this but not being technical none of it or the links makes sense. How can I resolve this as a stupid person? Thanks in advance!

Image doesn't start with perms wrote as:

:///*

or similar.

U have to do like

otiai10/capture-bug-in-chrome34@8fd7203

As per subject. Switches to another tab and tries to screenshot that instead.

Bug description

If one drags the thumbnail of the created pageshot and drops it somewhere in the filesystem (in the Mac Finder) a file with the proper naming scheme "pageshot of '<title>' @ " is written, but it is empty, has a file size of 0 bytes.

After the drag'n'drop action Chrome reveals the status bar, and shows the file like other file downloads. But in it's second row the troubled BlipShot file states "Failed — Blocked".

Reproducability

My conclusion

Very likely this is the bug condition:
If the protocol of a webpage is HTTPS then BlipShot fails, if it's HTTP then BlipShot works.

The permission issue seems to have nothing to do with the target (filesystem) but with the source (website), more specifically the scheme (HTTPS). And also nothing with the content type of the side, or a web browser plugin / extension conflict. The protocol raises the bug condition!

Target

I tried different locations on my computer. ~/Desktop, ~/Downloads, etc. They all had correct file permissions. Could not figure out any pattern.

Source

I had troubles reproducing this bug, sometimes BlipShot worked as expected and sometimes it failed with drag'n'drop to filesystem.

Success on i.e. http://origami.design/
Failure on i.e. https://www.flinto.com/

I tried more systematically. And then it occurred to me: It's the protocol which decides whether it works or not!

Affected versions

• Blipshot 1.1.1 (currently up to date)
• Chrome 54.0.2840.98 (currently up to date)
• OS: Both on OS X 10.9 Mavericks as well as on macOS 10.12 Sierra

Workaround

Right click the troublemaking file, then select "Save image as…"
This works, but you get an ugly filename like 3c428027-8d8e-43c0-a02d-441a5700664d.png and loose the more usable file naming scheme.

This affects many websites, but for me, the main problem are sites from the Stack* family. All of them feature a similar layout, with a sticky header that is always glued to the top of the screen. The problem is that this header gets repeated in the screenshot multiple times, more often than not hiding content behind it, e.g.

You can test this yourself by taking a screenshot of https://stackoverflow.com/questions/12503871/removing-path-and-extension-from-filename-in-powershell.

The workaround I use is to simply right click the header, click "inspect element" and then press the Del key to quickly remove it completely from the HTML before taking the screenshot. It would however be nice if the extension was able to do something like this automatically (or better, keep the header only on the top of the screenshot).

The day in the filename is off by a semi-random number of days.

I.e, screenshots taken today, the 28th of August 2018, are named pageshot of 'WFM' @ 2018-08-02-1016'57.png, but screenshots taken on the 24th were named pageshot of 'WFM' @ 2018-08-05-1534'52.png.

1. http://developer.chrome.com/extensions/tut_migration_to_manifest_v2.html
2. https://developer.chrome.com/extensions/manifest.html
3. http://developer.chrome.com/extensions/manifestVersion.html

Hey

I am over and over again experiencing this:

In the backend of a WordPress site. Clicking the icon to take a screenshot it moves the top bar down covering the top of the page. Making all the screenshots I use useless....

I just tried Blipshot with Chrome 17 on Mac OS X 10.7.3 and it works very easy and reliable but it makes a narrower screenshot than full width because it ignores the part of the scrollbar. If the extension would wait 1-2 seconds the scrollbar would be gone and it could take a screenshot over the full width.
Even if it takes a little bit longer that would be very nice.
Thanks

I go to this url: file:///C:/Users/John/Desktop/the%20guardian/index.html
When I click the blipshot icon, it tells me to reload the page which has no effect.

This extension solved my need very well. Thank you, everyone here.

Luakit users similarly need this.

I'm making this issue just as a pointer for others interested in this type of tool, and potentially in a simpler browser framework.

luakit/luakit#763

Seems to be capturing only the visible part of the tab, noticed on line 60 in screenshotter.DOM.js it says there's a bug where it doesn't screenshot correctly, is this what you meant by that? I could swear this was working a little while ago

I'm using Chrome Version 24.0.1312.52, on OS 10.7.5.

I've tried to screenshot the following sites:

• www.instructables.com
• http://www.samsung.com/uk/#latest-home

We go through the 'grab, make, done' steps, but no thumbnail is shown.

Any ideas?

CSV browser details from support details.com, pasted below:

OS Type,OS Version,Browser Type,IP Address,Javascript Enabled,Cookies Enabled,Color Depth,Screen Resolution,Browser Window Size,Flash Version,User Agent
Apple,Mac OS X 10.7.5 Intel,Chrome,31.24.7.150,Yes,Yes,24,1920 x 1080,1394 x 850,11.5.31,"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17"

Happy to attach images if helpful, but I can't think of anything that's relevant to attach off the top of my head…

For work I have to screenshot often github.com and most of the time the screenshot is like 15px thinner than the window (cropping on the right). How can I debug/help? Thanks!

I'm trying to take a full screen screenshot of several pages, and I only get the visible portion. This is an example of one:

http://www.flashmint.com/freebies/free-wordpress-theme.html

When I started the Blipshot extension in 2010 I had a lot of fun digging into Chrome API, and figuring out a quick and intuitive way to take screenshots. A lot of the extensions at the time were really complicated, and I needed something that just took a screenshot.

It doesn't seem difficult, but there are some nasty API required because the Chrome API never quite released the right tools to do this well. Lots of workarounds and adjustments.

Fast forward to 2022, after 12 years I managed to keep the extension running by keeping up with all the changes to the API needed, often in the form of additional restrictions or bugs. I feel 12 years is a quite a long time for an individual developer even if the extension is quite simple in its interface, and I'm proud of the work done and of the over 30,000 users I had over the years. Quite a testament to how good it was given I never publicized it or anything.

Today, Chrome requires another API change, with Manifest V3, and unfortunately this time it requires an extensive rewrite. In my initial analysis I feel it might be an almost complete rewrite to again work around sandbox and some structural changes. What was a fairly lean and smart plugin is now a massive drain on my time just to keep it running unchanged.

After quite some time of reflection and talking with some friends, I thus have taken the difficult decision to stop developing it, until the day Manifest V2 will be officially retired in January 2023 according to current timelines.

I'm glad this extension has been so useful for so many people.
Thank you everyone.

Are there any known conflicts with other extensions/plugins I should disable?

Hi,

I really like this add in. I want to use it several times a minute, but the timestamp is per minute. If I save multiple shots in one minute to one folder I can't because the file already exists.

Is there a way to either

• use a serial timestamp (1,2,3)
• use the seconds in the timestamp

Thanks a lot!

Because we would like sometimes to show the "over" effect of the mouse, it would be cool to take screenshots with a keyboard shortcut.

Error:

Unchecked runtime.lastError: This request exceeds the MAX_CAPTURE_VISIBLE_TAB_CALLS_PER_SECOND quota.

Introduced in Chrome 92:

• https://developer.chrome.com/docs/extensions/reference/tabs/#property-MAX_CAPTURE_VISIBLE_TAB_CALLS_PER_SECOND
• https://source.chromium.org/chromium/chromium/src/+/b7296443c150facf64930a561134643183d1d77c

Apparently Chrome was crashing when screen was captured too fast, so they just decided to throttle it.

I wonder when we're finally going to get a proper full page API, but for the time being, let's again look for another workaround...

Thanks to JTL for the report.

Keeps requesting to "reload the page". Blipshot still doesn't work immediately after reloading the page.

I'd love to be able to take screenshots of some UI elements that require hovering, which I can't figure out how to do with Blipshot. Blipshot requires clicking on the icon, which means I can't get a shot of the hover behavior.

If there were a hot-key or a way to do a delayed screenshot I could do it.

This is a great extension and I love that you've made the implementation so reusable and easy to follow! I did notice that some fixed elements such as side ads, video ads and footers tend to reappear in multiple stitched sections. Something with the BlanketStyleSet library?

Hello,
Blipshot worked correctly with Chrome 56, but hangs with Chrome 57 (Slimjet 14), on the make icon, for any page lengths
Sincerely

YYYY-MM-DD-HHMM'SS, i.e, 2018-08-02-1016'36, is a strange date and time format.

Preferably something like the ISO 8601 format (YYYY-MM-DDTHH:MM:SS i. e, 2018-08-28T10:39:01) should be used. I would also be OK with YYYY-MM-DD HH:MM:SS i. e, 2018-08-28 10:39:01, which is more readable.

The library screenshotter.*.js is currently only partially abstract.

To make it properly abstract, it requires to:

1. Move away the HTML writing of the screenshot from screenshotReturn
2. Extract the events that are triggering the UI class (badges)
3. Write some better documentation!