tab don't remember desktop view
-
hey everyone
can anyone confirm, that if I activate desktopview at a tab and I switch to other apps and come back to vivaldi, the tab has mobile view and desktop view is disabled (better: not enabled) again
android 11, newest vivaldi stable
-
I have switched to a few apps and returned to Vivaldi, only to find out the webpage still in Desktop view.
When I threw away Vivaldi and restarted it from scratch, though, the page opened in mobile view.Maybe what's happening to you is that, while you're in the other apps, Vivaldi gets unloaded to free memory (or simply because you have an aggressive OS - I remember I had a Huawei phone where even the simplest app switching and back would unload an app, I hated that). When you go back to Vivaldi, it gets reloaded again and the page is reloaded from scratch, in mobile view, could that be it?
I still think it's a bug, nevertheless. Or, at the very least, a feature request I would definitely vote for. Whether a page is being displayed in desktop mode or not should be part of the state stored by Vivaldi. I want to continue browsing where I was, regardless if the app has been unloaded or not (while we're talking about it, memorizing the position on the page would be nice as well).
-
@pauloaguia said:
Maybe what's happening to you is that, while you're in the other apps, Vivaldi gets unloaded to free memory (or simply because you have an aggressive OS - I remember I had a Huawei phone where even the simplest app switching and back would unload an app, I hated that). When you go back to Vivaldi, it gets reloaded again and the page is reloaded from scratch, in mobile view, could that be it?
I think you nailed it with more detail, thanks for testing it out!
I reported the same bug in march last year, but it was fixed. I don't know, if it's better to open a new one or re-open the old one (VB-64276) -
@derday said in tab don't remember desktop view:
I don't know, if it's better to open a new one or re-open the old one (VB-64276)
I don't know which one's better either, it would have to be someone from the dev team to give their opinion.
What I would say is that if you chose to create a new bug, to include a reference to the first one. If it is a regression to a previously known and fixed bug, it might be useful to know how it was solved the first time to figure out where to look for the problem this time.
-
I filed a new one (with reference to the old one): VAB-4441
-