ubuntu-webapps-bugs team mailing list archive
-
ubuntu-webapps-bugs team
-
Mailing list archive
-
Message #01200
[Bug 1353143] [NEW] Save/restore a webview’s state
Public bug reported:
We need a mechanism to save and restore the current session of the browser/webapp container.
For the browser, each open tab should be saved, whereas for the webapp container there’s only one webview to handle.
A naive solution is to persist the URL of each open tab, and upon
restore instantiate a webview and set its url property. However this
won’t restore the corresponding navigation history, nor the current
scroll offset or form data.
To implement this properly, we need to add an API in oxide that will
allow reading the current state of a webview as an opaque blob, and
writing the initial state at construction time. The API would look like
this:
property string initialState (writable during construction only)
function getCurrentState()
(see the full discussion at
https://lists.launchpad.net/oxide/msg00037.html).
** Affects: oxide
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Confirmed
** Affects: webbrowser-app
Importance: High
Assignee: Olivier Tilloy (osomon)
Status: Triaged
** Also affects: oxide
Importance: Undecided
Status: New
** Changed in: oxide
Status: New => Confirmed
** Changed in: oxide
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: oxide
Importance: Undecided => High
--
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/1353143
Title:
Save/restore a webview’s state
Status in Oxide Webview:
Confirmed
Status in Web Browser App:
Triaged
Bug description:
We need a mechanism to save and restore the current session of the browser/webapp container.
For the browser, each open tab should be saved, whereas for the webapp container there’s only one webview to handle.
A naive solution is to persist the URL of each open tab, and upon
restore instantiate a webview and set its url property. However this
won’t restore the corresponding navigation history, nor the current
scroll offset or form data.
To implement this properly, we need to add an API in oxide that will
allow reading the current state of a webview as an opaque blob, and
writing the initial state at construction time. The API would look
like this:
property string initialState (writable during construction only)
function getCurrentState()
(see the full discussion at
https://lists.launchpad.net/oxide/msg00037.html).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1353143/+subscriptions
Follow ups
References