We are not sure if accessing webView.page will ever be an useful API, therefore we should move it into experimental and leave it cooking for a while. :)
Created attachment 119051 [details] Patch
(In reply to comment #1) > Created an attachment (id=119051) [details] > Patch I had to change the tests and some other usages of page, but this is very straight forward. I've run the tests to make sure I didn't break anything. ;-)
Comment on attachment 119051 [details] Patch LGTM
Comment on attachment 119051 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=119051&action=review > Source/WebKit2/UIProcess/qt/QtPageClient.cpp:60 > - m_webView->page()->update(); > + m_webView->experimental()->page()->update(); It's ugly that we ourselves in our implementation have to use experimental API :) How about this: Keep the page() accessor in QQuickWebView, but remove the Q_PROPERTY (makes it disappear from QML). Instead add the Q_PROPERTY to to QQuickWebViewExperimental with a forwarding accessor.
Created attachment 119446 [details] Patch
Created attachment 119452 [details] Patch
Comment on attachment 119452 [details] Patch Clearing flags on attachment: 119452 Committed r103093: <http://trac.webkit.org/changeset/103093>
All reviewed patches have been landed. Closing bug.