WebApps remember the last page accross restarts, leading to potential dead ends
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| unity-webapps-qml |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Nexus 4, image 204.
Test case:
- Reset the Twitter app (rm -r /home/phablet/
- launch the Twitter app
- Try to find a "dead-end" page (eg. go see the Cookie policy at the "Sign In" screen then click on whatever external link in the Twitter help to left Twitter). Personnally I ended up on Google Play via an "Install App" link.
- Exit the App
- Relaunch it
- It still opens at the previous location, which therefore may not be Twitter. And, depending on the page you ended up, it may actually not be possible to go back to Twitter at all without manually removing the app data.
In my exemple, I now literally have a kind of "Goole Play WebApp" when I launch the Twitter WebApp.
The escaping problem is most likely another bug (?), but this one makes it worse because you can't event workaround it by "turning it off and on again".
| summary: |
- WebApps remember the last page accross restart, leading to potential + WebApps remember the last page accross restarts, leading to potential dead ends |
| Olivier Tilloy (osomon) wrote | #1 |
| Changed in unity-webapps-qml: | |
| status: | New → Invalid |
That’s intended (i.e. it’s a feature, not a bug).
The bug really is that you managed to escape the confinement of the twitter domain within the webapp (bug #1360462, which I confirmed). The webapp container is supposed to intercept navigation requests to other domains and redirect them to the corresponding webapp or to the browser.