Chrome Is Working On Tab Declutter On Android (windowsreport.com) 24
"Google is testing the ability to automatically archive and delete inactive tabs in Chrome on Android," writes Windows Report:
The experimental feature, called Tab Declutter, aims to simplify tab management by automating the process... After a set period of inactivity, Chrome will automatically archive inactive tabs. You will no longer see the archived tabs but you will be able to retrieve them if needed.
As for deleting the tabs, you can set Chrome to remove them after a longer period of inactivity. This feature will free up memory and improve the browser's performance. Obviously, you will have control over the archival threshold and the period of time after which the browser takes action... obviously, you will have control over the archival threshold and the period of time after which the browser takes action
As for deleting the tabs, you can set Chrome to remove them after a longer period of inactivity. This feature will free up memory and improve the browser's performance. Obviously, you will have control over the archival threshold and the period of time after which the browser takes action... obviously, you will have control over the archival threshold and the period of time after which the browser takes action
Do not want (Score:5, Informative)
My tabs are open for a reason even if I don't use them every day. Don't mess with them
Re: (Score:2)
Re: (Score:2)
Why tabs and not bookmarks?
Session Buddy (Score:2)
Session Buddy is good for proactive tab management.
As is vertical tabs in Brave / Firefox.
Re: (Score:2)
Based on the description, it sounds like they're trying to exactly replicate a feature already present in firefox for android.
Never cared for tabbed apps anyway (Score:2)
I have never been a fan of tabbed apps anyway. I like that it is there, but I feel nothing should be opened in a tab unless it is specifically requested to be in a tab. I much prefer completely separate instances of the application, especially on PC, but even with android devices, especially tablets where dividing the screen doesn't make it too small to easily see. I think tabbed applications happened when everything made the push to try to force you to run apps in full screen which I almost never do. Small
Re: (Score:3)
Tabs are just poor window management.
Even on a mobile form factor where fullscreen makes sense, tabs don't.
The idea of a 1:1 correspondence between apps, windows, and processes is misguided. Why shouldn't one app have multiple windows?
Web browsers in particular are glorified document viewers with delusions of being operating systems (although they are more like EMACS than vim nowadays, with the Lisp interpreter and web apps, so there is that), so why shouldn't each page be its own window?
Because of Apple,
Apple were late to the party on tabs (Score:2)
Browsers on the Mac did use one window per page. It made sense when the menu bar i
Re: (Score:2)
Browsers on the Mac did use one window per page.
That's only reasonable. One document, one window.
They've changed this in later versions of macOS to make it less obvious to the user whether an application is running.
I don't see how that is an improvement.
But anyway, I was talking about iOS. Android is rarely used as a desktop shell. (I should have been clearer about that.)
You close an application on Android by flicking it off the screen (swiping up on it) in the application switcher.
The direction differs between different manufacturers. I don't know why so many of them think they have to add their own clutter.
There is also the "close all" button.
The Android application lifecycle has no real end state, at least from the developer perspective, but a stopped app can be killed at a
Re: (Score:2)
Tabs are just poor window management.
Even on a mobile form factor where fullscreen makes sense, tabs don't.
Tabs are wonderful. They do exactly what I want them to do. I work in a web application all day (it is an interface to a centralized database, so it makes sense for it to have a web interface) and for various reasons it also makes sense for it to be full screen. The application is completely tolerant of multiple windows and the back button. Only in a couple of modal situations can I not go back, change some stuff, and submit the form again. Using it in a browser with tabs means I can rapidly access exactly
Re: (Score:2)
I open a new window for each group of data
I think I did mention that grouping is a good thing, and that window managers don't offer enough in that way.
But I also said that using tabs to do that is limiting.
For example:
drag a tab out into its own window
The other direction doesn't work, does it. Not an idempotent operation.
half-screening a window by dragging it against the appropriate screen edge.
A clumsy hack, compared to using a tiling WM.
it is an interface to a centralized database, so it makes sense for it to have a web interface
Why not use a proper graphical database client?
The application is completely tolerant of multiple windows and the back button.
I shudder to think why you thought that is even worth mentioning. I don't want to even imagine a non-parallel multi-user database.
Only in a couple of modal situations can I not go back
You mean it is broken?
When you say "modal
Re: (Score:2)
drag a tab out into its own window
The other direction doesn't work, does it. Not an idempotent operation.
What? yes, it does. You drag the tab into the window you want to put it back into. A window emptied of all tabs closes.
Big Idea (Score:3)
How about this wild crazy idea: When you close the program, not just flip away, actually close .... It closes the tabs.
Crazy I know. When a program is manually closed it actually gets closed.
Re: (Score:2)
Yes, crazy. When I switch to another window, I don't want to lose all the files I had open.
Android doesn't have the notion of actually closing an app. It has a back button, which may close a tab or a window, which may or may not end the underlying process group. An app can also be terminated at any time if it is in the background, to free up space for the app in the foreground.
Apple does have the notion of closing an app. It closes the app. When the app is opened again, it should start were it was stop
Re: (Score:2)
You literally prove my point.
No the 'close all tabs' is not what I want.
I want to 'swipe up from the bottom, hold, then let go. Swipe up on the app.' .... from android help center to "close app". This is different than your flipping away. It is intended to close the app....but doesn't.
I'm literally just asking the %@# browser to follow the stated design expectations. Automatically and permanently fixing the 'tab clutter' problem.
Re: (Score:2)
You literally prove my point.
You had a point?
I'm literally just asking the %@# browser to follow the stated design expectations.
It is intended to close the app....but doesn't.
Maybe because it doesn't mean what you think it does.
The Android app lifecycle has no designated end state. Any app in the background can be terminated at any time, and when put in the foreground again is supposed to continue as if it hadn't been. (Chrome breaks that expectation, by opening a new tab if it had been terminated in the meanwhile. So actually, the only way to prevent cluttering it is to not close it - except that doesn't work reliably: Just because it is still in the window s
Working on == Ignoring (Score:2)
Firefox already does this (Score:2)
and has for at least months, but I believe years
Now if it would just not punch my battery in the nuts
the problem (Score:2)
The problem with Chrome on android is if you look something up, then close the app, it keeps that tab stored. When you open chrome again, it opens a fresh tab for you. This leads to a bunch of open tabs showing things you looked up weeks ago.
Re: (Score:2)
So the solution would be not to reinvent the disastrous "declutter", but to open Chrome where it was closed, rather than with a new tab as it does.
How about (Score:1)