Open porg opened 7 years ago
Thank you! This is an amazing report, and I agree... there seem to be an issue there, sadly. :(
I wonder if Chrome changed something recently... I need to look into that.
Thanks!
You are providing this wonderful freeware which has helped me often enough already, so now it was my time to give back by thoroughly studying and reporting the bug.
Thanks for your appreciating response, all the best for fixing the bug!
+1 came here to mention the same thing.
Few things worth noting:
Odd. Thanks for the workaround!
@lippytak Nice to see that my workaround helps you out in the meantime. And good to see further debugging observations. @folletto Do our observations enable you to fix the bug? Or still in the dark?
These observations are very useful, unfortunately I haven't found yet a workaround, sorry ^^'
Any news?
Sorry I couldn't find time yet. I'm aware it has been a few months, I'm sorry :(
@lippytak HTTPS://github.com > Blipshot fails for me.
@folletto FYI: Extension Settings at chrome://extensions > Blipshot > Allow access to file URLs
is TRUE
. But nevertheless the bug behavior is unchanged.
I thought initially it was a matter of Content Security Policy but either I wasn't able to find the right setting in manifest.json
, or it's not the right solution.
However I noticed that if I disable the "nice name" javascript handler in actionDrag
:
e.dataTransfer.setData("DownloadURL", "image/png:" + filename + ".png:" + blobURL);
The image can be dragged and appears correctly. Just, has the ugly name. :(
Here the change: https://github.com/folletto/Blipshot/commit/c97e19500216b3b5d2e3bcd14674797025e7346e
I also managed to find a way to instantly download the image on click, which seems working on all sites. It's not drag'n'drop, but at least with one click it downloads.
I'll keep this issue open still, as the issue isn't really solved.
I haven't pushed any update to the Chrome Web Store yet. Still playing around it a bit.
Ok version 1.2 published on the store. As mentioned above doesn't "solve" the issue, but at least it's not stuck anymore:
http
works as usualhttps
works, but the filename is weirdhttp
and https
clicking on the image saves it in the default location, with the right nameI'm keeping this issue open as I want to try again to solve the https
drag issue properly.
I tested it, and it works as in your description. Would be glad if drag'n'drop with a meaningful name would work again, as this was a very time-saving feature of Blipshot!
I agree, I will try again to see if there's a workaround.
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 '
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
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.