The bug is potentially going to re-appear once statesaver is re-
introduced. When that happens, and if this bug is not fixed by then, the
consquence is that the Facebook webapp won't be automatically won't be
automatically restored to its previous state, if stopped by the
oomkiller.
I have triaged the bug based on that potential severity,
** Tags added: touch-2014-10-09 usability
** Changed in: webapps-core
Importance: Undecided => Medium
** Changed in: webbrowser-app
Importance: Undecided => Medium
** No longer affects: unity-webapps-qml
** Changed in: webbrowser-app
Status: New => Triaged
** Changed in: webapps-core
Status: New => Triaged
** Changed in: webbrowser-app
Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)
--
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to webbrowser-app.
https://bugs.launchpad.net/bugs/1347764
Title:
webapps user scripts overriding StateSaver saved url
Status in The Webapps-core project:
Triaged
Status in Web Browser App:
Triaged
Bug description:
placeholder bug for issue that has been discussed already:
webapps and webbrowser are now using StateSaver to restore previous url if
they are killed by oom killer. There is an issue with webapps that use user
scripts (currently Facebook) where the user script runs after the save url is
restored and overwrites it with it's own url. This will need to be updated to
honor the value saved by StateSaver, if present.
To manage notifications about this bug go to:
https://bugs.launchpad.net/webapps-core/+bug/1347764/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help : https://help.launchpad.net/ListHelp
