Please complete the following information when submitting a feature request or bug report.
Currently as I write this...
my client is on 7.0.104
web store is on 7.1.0
I didn't even know there were new versions until I was poking around for something else here.
So, I'm not sure what is the safe way for me to get the new update. If there's any way to nudge it, or simply rip all my settings/current data and put it in the new one after uninstalling/installing from the web store. 馃槮
Well, I was looking how to resolve a problem with TGS obviously switching focus to a tab/window being suspended and stumbled upon this issue. I've just successfully upgraded TGS with the following precautions:
It seems like the Chrome is running faster and things are cozy and startup time seems to be better - around 10 seconds with 366 suspended tabs restored.
So, save your session and upgrade, having these precautions in mind.
See this thread too for backup/restore and manual update suggestions
https://github.com/deanoemcke/thegreatsuspender/issues/526
Ditto, but from 6.30.
One of my browser profiles has upgraded to 7.1.0, but the other two are stuck on 6.30. I wonder if this is due to staged roll out, or if there's another reason. Based on this, all should have upgraded to 7.1.x.
@deanoemcke I also updated my ClutterFree extension to use message passing (#276 ) for unsuspending tabs.
This fails without warning for pre v 7.1.x users of TGS since default behaviour is:
null/no-response for _success_ in 7.1.x, butnull/no-response for no-op/failure in pre 7.1.0.I'm also having this issue on Chromium but I'm stuck on version 7.0.109.
When I open the background page
(chrome-extension://klbibkeccnjlkjkiokjodocebajanakg/_generated_background_page.html) and request an update check via the console, Chromium does not find any updates (I would expect update_available):
$ chrome.runtime.getManifest().version
"7.0.109"
$ chrome.runtime.requestUpdateCheck(function(status, details) {console.log(status)})
no_update
Which is pretty weird and I don't know why (maybe a Chrom{e,ium} bug?).
Anyway, at least in my case it seems to be a problem with Chrome/Chromium rather than TGS.
@sheershoff Apparently the focus-stealing bug is a known issue/regression. Unfortunately, it was a bug introduced as part of the fix to the "chrome stealing focus when tab suspends" issue: #865, according to author
as mentioned in this comment, the issue has been reported against chromium, so you may want to watch that as well.
This issue has been automatically marked as stale because it has not had any new activity for 180 days. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
Most helpful comment
Well, I was looking how to resolve a problem with TGS obviously switching focus to a tab/window being suspended and stumbled upon this issue. I've just successfully upgraded TGS with the following precautions:
It seems like the Chrome is running faster and things are cozy and startup time seems to be better - around 10 seconds with 366 suspended tabs restored.
So, save your session and upgrade, having these precautions in mind.