1033999 - Support State/Session restore for browser-element

Status: RESOLVED INCOMPLETE

(Core :: DOM: Core & HTML, defect, P2)

Description

[Kan-Ru Chen [:kanru] (UTC+9)]

We want to support session restore for the browser-element. Ie. when a app or browser tab is closed or killed, we could reopen it with session restored.

We probably want a new API to control this.

Comment 1

[[:fabrice] Fabrice Desré]

Kanru, I started to split the current fx desktop session store code to share the common parts in toolkit in bug 449967. Still no consensus on what's the right way to do it though.

What do you mean by a new API to control this? Something like an event triggered when the session is restored? or a way to opt-in/opt-out?

Comment 2

[Kan-Ru Chen [:kanru] (UTC+9)]

(In reply to Fabrice Desré [:fabrice] from comment #1)
> Kanru, I started to split the current fx desktop session store code to share
> the common parts in toolkit in bug 449967. Still no consensus on what's the
> right way to do it though.

Nice!

> What do you mean by a new API to control this? Something like an event
> triggered when the session is restored? or a way to opt-in/opt-out?

I think from the browser writer's point of view, it may want a way to opt-in/opt-out session restore.

Comment 3

[Kan-Ru Chen [:kanru] (UTC+9)]

Attachment: WIP Part 1. Move some SessionStore modules to toolkit

Comment 4

[Kan-Ru Chen [:kanru] (UTC+9)]

Attachment: WIP Part 2. Extract common data collector to toolkit

Comment 5

[Kan-Ru Chen [:kanru] (UTC+9)]

NOTEs to myself

Hypothetical steps to restore a mozbrowser iframe:

 1. Unregister the old frameLoader from BrowserElementParent.js
 2. Destroy the old frameLoader
 3. Create a new frameLoader & empty remote process
 4. Start to restore the session history, storage, load content, scroll position
 5. Done

Recreating a frameLoader seems easier than reinitialize one. The session data is currently stored in BrowserElementParent.js, it should send the data to remote at step 3.

Comment 6

[Ethan Tseng [:ethan]]

Confirmed with Kan-Ru offline, this bug is not on the road map.
It should not be a 2.5 blocker.

Comment 7

[Andrew Overholt [:overholt]]

Please feel free to re-open if we need this.