Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Back button close all the tabs #9

Closed
ariasuni opened this issue Dec 27, 2012 · 8 comments
Closed

Back button close all the tabs #9

ariasuni opened this issue Dec 27, 2012 · 8 comments

Comments

@ariasuni
Copy link

It's pretty annoying when pressing the physical "back" button, it closes all my tabs (especially when I have many tabs). The behavior here must be like the stock browser: close only one tab (but don't put the browser at background, this is annoying).

@Anasthase
Copy link
Owner

Well, technically, there is no "close all tabs when back button is pressed" thing, but this is a side effect. The app is closed, so the Android system clean up the app. And as Tint do not remember previously openned tabs, all tabs are lost. I think maybe the best things to do is to make Tint remember of tabs, and restore them at start-up.

For the background thing, this is the default behavior of all Android apps, when there is nothing more to "back", it goes to background and show the previous app. I don't want to loose this behavior, but maybe there can be a better behavior, like press back twice to go background.

@ariasuni
Copy link
Author

I loose my answer because of this "bug". Damn it. So I'll go fast.

The best is IMHO to do like the stock browser, keeping others tabs opened even in background. I don't know how they do that…
The easier is to "press back twice". Or another trick to prevent stupid users to do stupid things accidentaly and going crazy.
Restore the tabs isn't a good idea IMHO since we loose what we were doing, so it fix only part of the problem.

P.-S.: I like Tint Browser! (but only when I don't loose 5 minutes of typing!)

@Anasthase
Copy link
Owner

In fact i believe there is two use case here:

  • i'm typing something when i accidentally hit "Back", i expect to not loose what i was doing / typing when i return to the app;
  • I have some open tabs i want to read later when i accidentally hit "Back", i expect to retrieve all my tabs when i return to the app;

So the tab restore works for the second case, but not for the first. And i believe this can be a useful functionality.

I'll try something different for the first case, either override default behavior in order to not finish the activity, but simply "hide" it instead, or the double-back thing. Or maybe both.

PS: Thanks for your PS. Are you the same "Sinma" than here ?

@Anasthase
Copy link
Owner

Ok, so i just uploaded on the market a version where you do not loose everything when you press "Back". This is not perfect, but at least it can help until next "real" version.

@ariasuni
Copy link
Author

Yes, I'm the Sinma of Linuxfr.org (and many others websites)! If you want to talk about the bug I notice, it's also in the stock browser: some text area or part of text area become non-editable, which is very painful when you search some pr0n intellectual content on a search engine or trolling writing comments on Linuxfr.org.

I'll try the update when it's on F-Droid (and I'll rely on the clipboard for my prose).

@ariasuni
Copy link
Author

The new version is Awesome! Why do you said it's not perfect?

@Anasthase
Copy link
Owner

Because if the system kill the app while is in background, all tabs will be lost. But this is much better than before, i must admit. I close this one, if you're happy with the correction.

@ariasuni
Copy link
Author

Tabs restore would be great, but not very useful to me, because I don't kill the app and the app don't force close, and I'm very happy with it now.

However, you can keep in mind this idea for future improvement. Do what you want after all!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants