Alternatively, for the use cases not needing to be in-browser, why restricting to extensions? Your platform has full featured apps doing the job out of the browser:
"Save to Google Drive" will create screenshots when applied on common websites. I use this now instead of bookmarking, as the screenshots are OCRed by Google Drive, giving me a searchable archive of interesting sites!
Heh, so you take a text format, make a picture out of it and let google OCR back it to text? Are you sure you don't just want to save the HTML and resources (i.e. ctrl-s)?
A page nowadays is easily composed out of hundreds of different files, several MB in size. A jpg is small, easy to store and share. I'd go as far that the OCR of a screenshot gives me a ways better search base than the source code, with all its formatting, meta-tags, variable-names etc.
Unfortunately that's half broken since months (years?). It's not possible to take full page screenshots, and the option panel creates error messages all the time.
There is a fork out there, unfortunately it's not in the Chrome Web Store yet. Maybe it will if it gets some love from HN:
I am using Full Page Screen Capture[0], which is a similar extension, but it still asks for "Access your data on all websites" and "Access your tabs and browsing activity".
I find it very hard to verify that an extension needs that to take screenshots, but now I have disabled that as well.
I guess the only real way to fix this is using something like PhantomJS to take pictures of public websites.
It’s malware & spyware free. I built the extension to take a screen cap of a seating chart that I built as a web page for my wedding—since all the other extensions at the time were broken. Why a web page for my seating chart? IDK, I wanted to play with CSS3 columns, alas I should have used photoshop…
I have been contacted by people who want to buy the extension, but it seems too dangerous, since they could easily install their own malware—I wonder if anything like this happened to “Awesome Screenshot”? My own conscience and, more importantly, my personal brand is too important to me to sell it.
In terms of the permissions, when I built it, I had to ask for those permissions in order to make it work. If you find any changes to chrome permissions that let me ask for fewer, please let me know or, better, submit a pull request.
Also, instead of PhantomJS, if you have a Mac, try out `webkit2png`, which works great as long as you don't need to login or interact with a page before the screenshot:
