Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Disable reload of restored tabs. Disable reload when clicked.

  • 7 iimpendulo
  • 14 inale ngxaki
  • 1 view
  • Impendulo yokugqibela ngu PawNewman

more options

The question above may seem like two problems, but the issue is only one problem.


I have session manager and I want to use the cache to load my tabs when restored. Right now I have it where once restored, all my tabs don't reload on startup. Instead they reload when clicked.

Is there any way I can disable the reload portion when their clicked? I found no setting in session manager that disable this and I'm beginning to believe it's within firefox itself. I tried the tab mix restore option by disabling session manager and that also results in the same thing happening.

The question above may seem like two problems, but the issue is only one problem. I have session manager and I want to use the cache to load my tabs when restored. Right now I have it where once restored, all my tabs don't reload on startup. Instead they reload when clicked. Is there any way I can disable the reload portion when their clicked? I found no setting in session manager that disable this and I'm beginning to believe it's within firefox itself. I tried the tab mix restore option by disabling session manager and that also results in the same thing happening.

All Replies (7)

more options

Hi,

You can try Work Offline in File (Alt + F) before clicking on a tab. Firefox will try to reload the page from the cache, at least when the page hasn't expired yet.

The option for automatic/manual reload of tabs at startup is Don't reload tabs until selected in Firefox Tools (Alt + T) > Options > General.

Options > General

Tools > Options

more options

That doesn't seem like a very elegant fix - you'll be constantly switching offline \ online.

Any advances would be greatly appreciated!

more options

Please help! This is a very annoying bug in the new firefox versions. I always had a lots of tab open and after restarted firefox they just loaded from the CACHE!

This is very important because:

- it's slow to wait for every tab to load when i click or all of them at startup, and in the 99% of the cases the page didn't changed, maybe just it's modified time since a php/asp page can change, but not the content, and the most importnat, that i didn't wanted to reload them.

- if i have a lot of login protected page than as i start firefox after my login session is over then it will reload all my pages and i totally LOSE every information. I will have only 30 login page tab....

I hope that there is a solution for that. Nowdays 1GB+ cache is not a problem so it can work with a lots of tabs. The only thing i can do now is to HIBERNATE my PC every time :( So actually i don't close firefox... If there is no settings now, please implement a very simple "hibernation" hidden settings. But i think it's a very common problem, not just mine.

Ilungisiwe ngu haliferi

more options

Have exactly the same problem. Using session manager and restoring earlier sessions won't work properly unless you click on the tab to make it reload the earlier session.

more options
more options

Thank you, but it's a solution for speeding up firefox start, but not related to the problem. If you enable this settings then pages are reloading when you select them.

The problem is with reloading and not loading into the memory. I think the best way to image it, is the hibernation that i mentioned. So you start firefox, and you get your pages back, in that status and content as you had them before you closed firefox.

The firefox setting you suggested can help in this case too, to spare your RAM, and load only the pages you wan't to use.

more options

Quote: christianhberg "I found the solution:

http://lifehacker.com/5859489/make-firefox-start-quicker-by-only-loading-tabs-as-you-use-them "


Session Manager does this by default I think. It doesn't address the issue of loading from cache. Certain cache elements are sometimes loaded such as where your scrollbar(where @ on the page you were located) location was. Sometimes I don't even get that and it seems to be a toss up.

Ilungisiwe ngu PawNewman