Using even an old captureVisibleTab (but faded out to indicate so) would be better than no screenshot due to resource concerns about thegreatsuspender HOT 4 CLOSED

Cheers for the link. I was aware of this method, however it only lets you capture the image of a visible tab, not one that is not selected.
I am working on a new version (v5.0.0) that contains a new option to set the screenshot quality quite low which should help with memory optimisation while still allow a screenshot preview.

from thegreatsuspender.

Why not use captureVisibleTab if it becomes visible, as it often will be at some time? Surely it would use less resources than computing the HTML all again, and would work with flash sites and more images etc?

from thegreatsuspender.

Are you suggesting that if you suspend the current (visible) tab, it uses the captureVisibleTab function, and if you are auto-suspending a hidden tab, that it uses the html2canvas library?
This would be very easy to do. I just wonder how often people are suspending the current tab - and it may seem odd that sometimes the screen capture looks a certain way and other times it's different?

from thegreatsuspender.

I'm saying perhaps most tabs are visible sometime, at some stage of their life, right? It would probably be more accurate and less resource intensive to use captureVisibleTab in those (perhaps the majority) of cases.

from thegreatsuspender.