hi,
i really love this addon, but problem is, it blocks another important addon i´m using:

https://chrome.google.com/webstore/detail/icinga-status/imaieifkljkcdepgaeommbdgihollphm

i don´t know where the problem is, but the icinga addon is unable to load the data when staying alive is active.

i am not able to debug this, please help!

btw... i don´t understand that this is even possible in chrome... ;-((

thx

I was using it fine to keep looged on a webtool we're using and now it stopped working.
Another colleague of mine reported same issue with a different webtool so maybe it's something on the extention or how chrome is dealing with the extension.
I've notice that the counter stopped at 0 but it didn't refreshed the page.
Please see:

Thank you

Save settings to global user profile storage api, not just to localStorage.
http://developer.chrome.com/extensions/storage.html
also use sync option

When using only Foreground Page Reload, the first time you manually trigger it by navigating to a matching URL, it works. But doesn't do anything after that, thus defeating the purpose of the plugin. You have to manually surf again to the trigger url to get it to go again.

Help me how it work the extension i dont know who to use it someone help me

The extension seems to be case sensitive with the url. Which I think should not, or at least to have an option for case sensitivity.

I am receiving the following console error on every page that is loaded when the Staying Alive extension is enabled.

Unchecked runtime.lastError: The message port closed before a response was received.

1. Create a two or more rules
2. Enter in all Trigger Url options same address. e.g. https://www.google.com/
3. Save
4. Go to this address
   Result: only last created rule works.

It's becoming really annoying! At first I thought it was after an update, but it happens every day. Can this be prevented/improved?

if I use "http://localhost:8080" as trigger URL plugin does not start background requesting for URL based on given. E.g. "http://localhost:8080/test" does not start requesting.

"There are no background requests and no scheduled page reloads running at this time. Click on Settings button above to view or add background rules" even after i did the settings multiple times. I do not know if the add-on is running or not. Do I have to restart the system?

I installed in the new Chromium-based Edge browser and it will only run once. It will only run again if I open settings, make a change and set it again.

Since the EU forces all banking session to end after exact 5min:00seconds, the max fitting keep-alive interval your browser add-on offers is 4min. Yet, using 4minutes means loosing about 20% time for typing text and numbers into all kind of fields of a bank form (or looking up numbers that one need to fill their forms). Even 5minutes is already a very short amount of time, if one has to lookup account numbers, formulate concise text references, etc.

Thus, I kindly ask to include a reload timer allowing setting minutes plus some seconds.
If you are afraid of server overloads, you could restrict it in a way that a minimum interval has to be always 60 seconds (1min.) so that people do not run a 1sec keep alive script.

Alternative:
If allowing setting seconds cause huge re-coding/extra work to you, could you simply offer a switch/checkbox that can turn on a predefined foreground timer reloading the foreground page every 4minutes and 58seconds? This would do the job as well.

(by the way, I never got this background keep alive working in any kind of my sessions of different accounts... Which servers allow keeping sessions alive with background refreshes only? I am just curious. My bank sessions and other governmental sessions all ignore background reloads)

I see this hasn't been maintained since 2013 and I'm interested in maybe making some updates. First things first however, I don't see any license info. It seems to be abandoned. Can I assume that this code is public domain?

It would be nice if it would beep only when the tab is the front-most tab, in other words, when I'm actively using the reloading tab.

For example, I have a legacy webmail system on autorefresh so it doesn't log me out for inactivity, and only want it to warn me audibly about refresh when I'm actively using it. For example when composing an email.

It seems to be matching the urls case insensitive, but thats not the best idea. It is possible that parts of the URL are case sensitive, so its best to build this in a case-sensitive manner. Store the actual user input, do not convert to lowercase, match with case-sensitivity for a less buggy result in edge case scenarios.

The program does not recognize when the website has changed due to user input and will continue to try and refresh even if the user is actively using the page.

Please Please update this wonderful extension to be compatible with new chrome version

Add option to define extra header with value to be sent in background requests.
This will be useful to "let the server know" that this is a auto-background request.

In development environment it may be desirable to ignore these automatic background requests, for example not to write anything to logs for these requests.

Hello! Love your extension and went to recommend it to someone and realized that it's currently 404ing when trying to view it in the Chrome Web Store. Wanted to bring this to your attention incase you didn't know. And if you do know, I was hoping you could share the reason please. Thanks!

Need to defeat websites that have inactivity timeouts implemented on client with javascript. The way to defeat this is to just have the pages reload after "n" seconds.

With client-side rules a small javascript will be injected with pages that match the url pattern. It's important to match pattern and not exact url because when user browsing pages on the site we want to inject javascript in all pages of the domain.

The javascript will start a countdown and when about 30 seconds is left till reload a small div will appear in top or bottom of page saying "Page will reload in 30 seconds [Cancel button]"

If Cancel button not clicked that page will just reload in browser.

Under "Extra Header" settings, you have the following:

"You may define an extra http header to be sent with background requests
This may be useful if you sending background requests to your own server
and want the "let the server know" that these are special type of requets
Ignore this option if you not using this extension to communicate with your own server"

What it should probably read is like so:

"You may define an extra HTTP header to be sent with background requests.
This may be useful if you sending background requests to your own server
and want to "let the server know" that these are a special type of request.
Ignore this option if you not using this extension to communicate with your own server."