Open quantuumsnot opened 6 years ago
Can you give a bit more information on your proposition? Like some examples perhaps? I do not understand what you mean by:
so this doesn't save traffic, only memory for a given N minutes.
And I also dont see the relationship between how long you spend on a focussed tab, and the time it should take to suspend a tab in the background. Why would you want these two things to be the same?
I'll try ... From a user's perspective it's cool to have the feature to automatically lower the CPU/memory usage when there's no actions in the browser or only one tab is active. Better UX, but the "issue" with this approach is in the average suspended time of inactive tabs. Users like me almost always read many and long articles combined with a shorter ones - expressed in time it is between 5-10 minutes to an hour in reading. This time doesn't help when in the middle of reading the user must switch to another tab to quickly check more info. What happens after that is the following:
So, I am proposing to add option to choose suspended time based on collected average suspended time per tab, plus enhancing it using classifier based on the type of the page (there's an exception, for example programming articles are from micro-size to a huge novel). This is possible with check for a specific words in
1) please refer to this open issue: https://github.com/deanoemcke/thegreatsuspender/issues/265
2) this sounds like a bug (not always auto-reloading). Most probably it is caused by this issue: https://github.com/deanoemcke/thegreatsuspender/issues/519 Also, there is already a feature that auto-scrolls to the same location on the page before the tab was suspended. so you shouldn't have to rescroll down like you are doing. This is a bug if so, and should be reported in a separate issue.
3) this sounds like a repeat of issue 1? you would like to save the suspended tab contents saved to disk so that you can do an offline reload? that would make it irrelevant whether the page had become unreachable.
I'm sorry, but I am still not seeing exactly what issue you are trying to solve. The points you raise (1,2,3) do not relate to the tab suspension timer. Are you suggesting that the time to suspend should be based on how long a the user has a specific tab focused (while unsuspended)?
I can't see the relationship between the time a user spends READING a tab, and the time it should take for that tab to be suspended automatically in the background. Just because I have opened a tab that I will spend 10 minutes (on average) reading, does not mean that that tab should be automatically suspended after looking at OTHER tabs for 11 minutes..
i think the general idea would be automatically clustering tabs and not suspending any while any tab in the cluster is focused. however, that would require quite an insane effort to implement, so i'd defer to explicit grouping - by window, as proposed in #818. wontfix?
Noticed that not a single one of drop-down "minutes" options are working for me (my reading time is between 5min and hour-hour and a half, so this doesn't save traffic, only memory for a given N minutes). Is there a chance to add an automatic simple suspend timer based on mean tab defocus time?