Enforce better handling of normal browsing session history storage during private browsing
Created by: TartanSpartan
- Device: Any
- Channel: Any
- Build: Any
Steps to reproduce
Go to the internet browser. Let's say you have 5 tabs of stored session history in normal browsing. Now open the private browsing mode. Swipe from the right, then close the normal browsing window. You are left with only the private window. Go to another app which can send a link to be opened in the browser; Dekko, or Web Telegram, say. Open the link.
Now, I'm going to change things up a little and invert the actual and expected behaviour sections' order relative to the template. This is to better explain what happens, and then how it should be corrected.
Actual behaviour
The link will be opened in a new normal browsing window. BUT! It has wiped the original 5 tabs, and I don't think they are recoverable; perhaps they might be stored in some obscure file deep within the file system, but even if they are, this self-evidently does not make them easily recoverable. This is unacceptable. I am quite sure (although not currently able to test) that if these steps to reproduce were repeated on x86 Ubuntu, using Firefox as the browser, the same thing would not happen. Or on other operating systems. So it should not happen in Ubuntu Touch, either. The user's current stored browsing session history should be respected, and not wiped unless they explicitly instruct the browser to do so.
Expected behaviour
Good question. Either, the link should be opened within a new tab of the private browsing window (and the only window) you had currently active; or, the normal browsing window should be called up again, with the original 5 tabs, and with this new link now forming a 6th tab in addition to that. I note that when I send a link to Firefox from desktop Telegram, it will open in a normal browsing window, rather than the private one. So, my expectation corresponds to the latter of the two options I propose here.