diff options
| author | Jocelyn Turcotte <jocelyn.turcotte@digia.com> | 2014-03-21 14:43:21 +0100 |
|---|---|---|
| committer | The Qt Project <gerrit-noreply@qt-project.org> | 2014-03-31 16:43:59 +0200 |
| commit | e9575322f8068b2dd2bc0b30a0f444f769a861b9 (patch) | |
| tree | 1a6fbc4a8cb71d10f436265d20bcb1538e836220 /src/webenginewidgets/api/qwebenginepage_p.h | |
| parent | 3f69bf43c45e54789ce6cdc4a2f01ea129e6287c (diff) | |
Implement QWebEngineHistory serialization
This does uses logic taken from Chromium's state save and restore
code. The history version is incremented from the same method in
QtWebKit in cases where the application would try loading a stream
from a previous version using QtWebKit.
In all cases where Chromium does a restore of a serialized history,
it does so on a fresh WebContents instance, thus we must do the same
and some of the initialization code has to be updated.
Change-Id: I45abb052073bd44c9cb47bc2abcf4b558fe3dbbd
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>
Diffstat (limited to 'src/webenginewidgets/api/qwebenginepage_p.h')
| -rw-r--r-- | src/webenginewidgets/api/qwebenginepage_p.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/webenginewidgets/api/qwebenginepage_p.h b/src/webenginewidgets/api/qwebenginepage_p.h index a69866cbd..927519008 100644 --- a/src/webenginewidgets/api/qwebenginepage_p.h +++ b/src/webenginewidgets/api/qwebenginepage_p.h @@ -142,6 +142,7 @@ public: void _q_webActionTriggered(bool checked); WebContentsAdapter *webContents() { return adapter.data(); } + void recreateFromSerializedHistory(QDataStream &input); QExplicitlySharedDataPointer<WebContentsAdapter> adapter; QWebEngineHistory *history; |