Thegreatsuspender: Suspended window pushes to front now, s/b be silent in background!

Created on 4 Aug 2019  Â·  8Comments  Â·  Source: greatsuspender/thegreatsuspender

Please complete the following information when submitting a feature request or bug report.

  • Extension version:
  • Browser name & version:
  • Operating system & version:

And please also do a search for your request/bug before create a new one thanks!

stale

Most helpful comment

Actually fixed the problem by removing the extension and installing it again. I had the same issue as in https://github.com/deanoemcke/thegreatsuspender/issues/865#issuecomment-510102476

All 8 comments

My work was disrupted several times lately by windows pushing to the front when suspended. Suspension timeout should be in the deep background!

@deanoemcke This effects me as well.

Does this have to do anything with any updates in Chrome?

Extension version: 7.0.109
Browser name & version: Version 76.0.3809.87 (Official Build) beta (64-bit)
Operating system & version: macOS Mojave 10.14.5

Having the same issues after updating Chrome to 76.0.3809.87. Really annoying. Have to disable the extension for now :(

Actually fixed the problem by removing the extension and installing it again. I had the same issue as in https://github.com/deanoemcke/thegreatsuspender/issues/865#issuecomment-510102476

I'm trying that, but note that all suspended tabs are closed!  You might want to momentarily unsuspend them all before tossing the extension/plug-in!

-----Original Message-----
From: Joonas Kokko notifications@github.com
To: deanoemcke/thegreatsuspender thegreatsuspender@noreply.github.com
Cc: DGPickett dgpickett@aol.com; Author author@noreply.github.com
Sent: Tue, Aug 6, 2019 4:12 am
Subject: Re: [deanoemcke/thegreatsuspender] Suspended window pushes to front now, s/b be silent in background! (#968)

Actually fixed the problem by removing the extension and installing it again. I had the same issue as in #865 (comment)—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Per @joonaskokko's suggestion, uninstalling and reinstalling the extension, it fixes it.

@DGPickett Being a maintainer of a different, unrelated repo, I can tell you that by not fully completing the original issue template is not at all conducive to getting attention on this issue. NEVER skip the issue template.

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.

Was this page helpful?
0 / 5 - 0 ratings