My OperaYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
A derivative of "Don't load tabs until selected"
As per this thread: http://my.opera.com/community/forums/topic.dml?id=1245872I generally start up Opera with 30+ tabs. I'm on a very tight bandwidth cap and I do not want all those tabs loading every time I start the browser, I'd prefer the tabs to remain unloaded or at least to load cached content only.
I use a workaround every time I open Opera whereby I disconnect my internet, start up Opera, wait a few seconds for all the tabs to finish loading cached content, then I re-enable the internet connection. I have do admit that this is a rather hideous workaround, but I see no other way to avoid the issue.
I was just wondering if it is possible to interrupt page loading on startup by use of an extension.
PS. Yes I've heard of tab vault. No, it (tab vault) does not solve my problem.
I tried making an extension to help with this earlier. It would have stopped tabs as they loaded, then reloaded them later. The problem was, Opera loaded extensions fairly late into the startup process, so it didn't reliably work. I don't know if this has improved any in recent versions of Opera.
Opera 12.15 - Win 8 Pro x64 All my Opera tools -Tab Vault: Save tabs for later -AutoStack: tabs opened from a stack stay there
That's not the problem. The injected .js files are loaded as each page loads, so you could just call window.stop() on every single tab, (this isn't an ideal solution, since it can't prevent some parts of the page from being loaded; many of the web requests will still be sent) but the extension's background script can take a while to start up. To coordinate all the tabs so that, for instance, the focused tab continues to load, but all others are stopped, you need to communicate with the background script.
When I tried this in Opera 11.6x, Opera prioritized loading each page, so by the time the extension loaded, stopping pages was pointless. Also, sometimes the early messages from tabs to the background script would be lost completely. Hopefully this is a little more reliable in Opera 12, but extensions' background processes still appear to be initialized later.
When I tried this in Opera 11.6x, Opera prioritized loading each page, so by the time the extension loaded, stopping pages was pointless. Also, sometimes the early messages from tabs to the background script would be lost completely. Hopefully this is a little more reliable in Opera 12, but extensions' background processes still appear to be initialized later.
Opera 12.15 - Win 8 Pro x64 All my Opera tools -Tab Vault: Save tabs for later -AutoStack: tabs opened from a stack stay there
@spadija do you tried to use urlfilter ?
ex:
- opera onClose -> urlfilter += * <-- block all url
- opera onOpen -> wait load -> urlfilter -= * <- disable blocking url
- opera onTabFocus -> load if not load
ex:
- opera onClose -> urlfilter += * <-- block all url
- opera onOpen -> wait load -> urlfilter -= * <- disable blocking url
- opera onTabFocus -> load if not load
Opera doesn't have an event to listen for the browser closing though. The best you could do with urlfilter is to block all on startup and hope it happens before any tabs start to load.
Opera 12.15 - Win 8 Pro x64 All my Opera tools -Tab Vault: Save tabs for later -AutoStack: tabs opened from a stack stay there
Originally posted by spadija:
block all on startup
OK, I will try it.
What event to use for the release/unblock ?
Originally posted by ImmortalPC:
Originally posted by spadija:
block all on startup
OK, I will try it.
What event to use for the release/unblock ?
I have no idea.
Opera 12.15 - Win 8 Pro x64 All my Opera tools -Tab Vault: Save tabs for later -AutoStack: tabs opened from a stack stay there