Force all links opened with 'open link in new tab' to auto-suspend immediately

[ghost]

Hello.
Is it possible to open new tabs without the context menu without being frozen?
It is very inconvenient to open each tab with the context menu. I want to make it easier. It's real?

[deanoemcke]

Sorry, I dont understand your question.
Why are you opening new tabs via the context menu?
It doesn't sound like your issue has anything to do with this extension?

[ghost]

I want to be able to open the tabs frozen without the context menu. Is this possible?

[deanoemcke]

This is possible - depending on the implementation. I don't think I can specifically override the 'ctrl+click' functionality, but i could add an option so that all new tabs that are opened but not given focus are automatically suspended. Is that what you are looking for?
I'm just not sure this would be a good idea as it could result in some confusion for users..

[ghost]

Yes, it would be nice to see this implementation. I would be pleased.

[dumblob]

Raising my hand for this (currently I live with Native Lazy Tabs extension for this).

[deanoemcke]

How about just setting the 'time to suspend' to 20 seconds? Does that give you a similar outcome?

[dumblob]

@deanoemcke unfortunately not, because in my case the main purpose is to prevent loading of hundreds of tabs after a Chromium (re)start. Without that it gets extremely slow, clunky, downloads hundreds of megabytes of data immediately (even though I won't use half of the tabs in the next few hours) and is way more prone to session loss in case something bad happens to the browser process(es) (it's not a theory - I've lost my "tabs" already several times before I started using Native Lazy Tabs).

[deanoemcke]

@dumblob it sounds like you're speaking of a slightly different feature. that is, automatically suspend all tabs on startup. this is already a separate issue: #49

I'll add some info about Native Lazy Tabs there.

[dumblob]

@deanoemcke well, it's though the most frequent use case of mine, but curiously this issue caught my eye, because I'm very often using the workflow in which I open e.g. 60 new tabs from a search engine page and first then I'm checking what is in those tabs. And because opening the links one after another very quickly has the same effect as when I (re)start Chromium, I mentioned the restart as it's easier to comprehend.

[deanoemcke]

@dumblob ok understood. but there is quite a difference in those two scenarios. opening 60 tabs one at a time from search results is a much more staggered process, and therefore produces much less load on the system.

for this new scenario, are you aware of the right-click 'open in new suspended tab' option? it will cause the link to open in a new tab, and as soon as it's loaded, it will immediately suspend it. i suspect if you do this for a whole lot of links manually, you'll have the first ones suspending pretty early on in the process.

the only downside to this is having to open each tab via a right-click menu option which may be cumbersome if you're used to using something like cmd/ctrl+click, or using the middle mouse button.

if this is your situation (ie: the existing 'open in suspended tab' functionality is not good enough), then this gitHub issue is to address exactly this. It's saying, when i choose perform the 'open in new tab' action (regardless of how i do this), then actually load the tab and subsequently suspend it.

[dumblob]

for this new scenario, are you aware of the right-click 'open in new suspended tab' option?

Well, I'm using TGD (which doesn't support this option) for about two years already and forgot about this option in TGS. Thank you for the reminder.

That would definitely cover part of the cases. All the rest would be complicated as I'm using cVim and therefore it would be useful for me to either allow cVim to run the function from TGS (which is IMHO not allowed due to security reasons) or just making this functionality independent from any extension (e.g. by autosuspending/autodiscarding the tab immediately after it has been opened in the background which is what this GitHub issue is basically about).