DocShell/Fastback: Difference between revisions
< DocShell
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
These functions are called from <code>nsDocShell::RestoreFromHistory</code> or <code>nsDocShell::SetupNewViewer</code> (that latter one doesn't call Destroy?). Things are only saved if <code>mSavingOldViewer</code> is true (otherwise, <code>null</code> is passed to Close). | These functions are called from <code>nsDocShell::RestoreFromHistory</code> or <code>nsDocShell::SetupNewViewer</code> (that latter one doesn't call Destroy?). Things are only saved if <code>mSavingOldViewer</code> is true (otherwise, <code>null</code> is passed to Close). | ||
Saving will always save to <code>mOSHE</code> | |||
== Restoration from history == | == Restoration from history == | ||
Revision as of 19:16, 5 August 2005
Saving to history
The nsIContentViewer saves itself to the SH Entry. It gets an SH Entry in its Close function as an argument, and saves itself there in Destroy.
These functions are called from nsDocShell::RestoreFromHistory or nsDocShell::SetupNewViewer (that latter one doesn't call Destroy?). Things are only saved if mSavingOldViewer is true (otherwise, null is passed to Close).
Saving will always save to mOSHE
Restoration from history
nsDocShell::InternalLoad checks whether the load is a history load and if so, whether it has a cached presentation.
It then calls nsDocShell::RestorePresentation, which calls nsDocShell::BeginRestore and if that succeeds, posts an event to call nsDocShell::RestoreFromHistory.
--Biesi 11:26, 5 Aug 2005 (PDT)