4 ms·

Turned that off almost immediately. Sounds good in theory, but if a suspended page has a heartbeat of any sort, it has to reload when you return to it. If that

Turned that off almost immediately. Sounds good in theory, but if a suspended page has a heartbeat of any sort, it has to reload when you return to it. If that page is an infinite scroller, or if you've hit the "load more" button a couple of times, well, so much for starting up again where you left off.

kranner 10y ago
You can whitelist certain pages permanently which is what I do for the Twitter homepage. You can also keep them active for the current session only.
- welanes 10y ago
  I thought that would do it but when you understand how you (I, at least) browse the web this feature became annoying, fast. Working on Nitrous IDE, take a break to read an article (on a page never before visited so not whitelisted). Check the Disqus comments, the article mentions a book on Amazon, check that out....oh no, my IDE page has just gone to sleep, now I have to reconfigure it again. Ah the article page went to sleep too, now I need to find where I am in the comments. Throw in the time for the pages to reload as well, and you can see how this could get frustrating.
nfriedly 10y ago
Mobile browsers already suspended most background stuff, and it occasionally does cause issues like that, but usually it just works. I learned this out a few years ago when trying to figure out why my metrics sometimes reported mobile visitors with load times of hours or even days... Turns out that they opened the site and then switched tabs/apps before it finished loading. Everything except that metric worked fine. I added a heartbeat just to detect that, and it worked without introducing any extra reloads.
- takno 10y ago
  This always drives me mad. It's particularly bad if I'm trying to read content sites on a train or somewhere with patchy reception - open half a dozen tabs to give me something to read while I'm disconnected, and then switch to them only to see the content disappear before my eyes. I'd nominate it as literally the worst thing about mobile browsing
mynewtb 10y ago
Only if the infinite scroll is of the sort that should not exist. User friendly solutions update the url.

kranner 10y ago

You can whitelist certain pages permanently which is what I do for the Twitter homepage. You can also keep them active for the current session only.

welanes 10y ago
I thought that would do it but when you understand how you (I, at least) browse the web this feature became annoying, fast. Working on Nitrous IDE, take a break to read an article (on a page never before visited so not whitelisted). Check the Disqus comments, the article mentions a book on Amazon, check that out....oh no, my IDE page has just gone to sleep, now I have to reconfigure it again. Ah the article page went to sleep too, now I need to find where I am in the comments. Throw in the time for the pages to reload as well, and you can see how this could get frustrating.

nfriedly 10y ago

Mobile browsers already suspended most background stuff, and it occasionally does cause issues like that, but usually it just works. I learned this out a few years ago when trying to figure out why my metrics sometimes reported mobile visitors with load times of hours or even days... Turns out that they opened the site and then switched tabs/apps before it finished loading. Everything except that metric worked fine. I added a heartbeat just to detect that, and it worked without introducing any extra reloads.

takno 10y ago
This always drives me mad. It's particularly bad if I'm trying to read content sites on a train or somewhere with patchy reception - open half a dozen tabs to give me something to read while I'm disconnected, and then switch to them only to see the content disappear before my eyes. I'd nominate it as literally the worst thing about mobile browsing

mynewtb 10y ago

Only if the infinite scroll is of the sort that should not exist. User friendly solutions update the url.