feat: option to disable double back to close tab

[leo-060]

When you click on some links, the link is opened in a new tab. To go back to the previous tab I need to swipe back two times to close the new tab. Please give an option to disable it. Thanks

[FaFre]

You can just swipe right or left the app bar to switch (similar to alt + tab). Does that solve your issue?

[leo-060]

Swiping on the tab bar does not close the new tab. On other browsers like Firefox, I can close the tab and go back to the previous tab by swiping back once. Here, I need to swipe back twice. Though I can achieve the same behavior here by tapping three dots + close tab.

[leo-060]

I have tried the latest alpha. There is indeed a disable double back to close tab option, but the back button behavior is not what I intended. Also users are not able to quit the app by pressing back anymore.

I compared the behavior of the back button in other popular browsers vs WebLibre. Here is a summary:

1. In other browsers, after you open a new tab (could be a homepage or a custom page) then press back once, you exit the browser without closing the tab. In WebLibre, you open a new tab by directly typing a URL, then you press back twice to close the tab.
2. In other browsers, after you open a link in a new tab then press back once, you close the tab and return to the previous tab. In WebLibre, you press back twice to close the tab.
3. In other browsers, when you open an external link (for example clicking a link in an email), you open it in a custom tab / in-app browser. In WebLibre, when you open an external link, you open it in the full browser. Also, there is a bug (?) that pressing back here instantly exits the browser without closing the tab.

Now that I think about it, WebLibre’s implementation is more consistent as double back always corresponds to closing tab and you would not close the app by accident. Therefore I would like an option in the settings for the back button to follow the behavior of popular browsers in 1 and 2, because that is what other users expect when they are coming from these browsers.

[FaFre]

Thanks for adding those insights! I added the double back because I sometimes mistakenly closed tabs on other browsers. Once getting used to that it is more "secure" when filling forms or something. For point 3. I think we can consider adding a dialog here before invoking the system navigator that replaces the double back with options for close, return and cancel. Sometimes when opening OTP links you want to get rid of them asap (but then on the other hand you can just choose to open them in private), while articles you want to stay when returning to the app.

[leo-060]

When you click on a link in a website, some links load in the same tab while some open in a new tab. You do not know which one of the two would occur before clicking on the link. And there is not much visual to tell them apart, besides the number of tabs shown in the tab button. Other browsers provide a unifying behavior that a single back press always go back to the previous page.
For point 3, I think other browsers' implementation is more natural. The link would be opened in a custom tab. If you want to close it, you press the back button or the x button in the corner. If you want to save the page for later, you open it in the full browser. Your suggestion of the back button would be inconsistent with the double back to close behaviour. Also I think it would be annoying to further click something in the dialog to close after you press the back button.