From e9575322f8068b2dd2bc0b30a0f444f769a861b9 Mon Sep 17 00:00:00 2001 From: Jocelyn Turcotte Date: Fri, 21 Mar 2014 14:43:21 +0100 Subject: 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 --- src/webenginewidgets/api/qwebenginepage_p.h | 1 + 1 file changed, 1 insertion(+) (limited to 'src/webenginewidgets/api/qwebenginepage_p.h') 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 adapter; QWebEngineHistory *history; -- cgit v1.2.3