diff options
author | Milian Wolff <milian.wolff@kdab.com> | 2014-07-03 19:12:37 +0200 |
---|---|---|
committer | Allan Sandfeld Jensen <allan.jensen@digia.com> | 2014-08-16 09:49:41 +0200 |
commit | 05ea746d3042d1409305bc1ebcaf15095870b6d9 (patch) | |
tree | 5155938d7e853d96a6a4de44c314d715b88d547c /Source/JavaScriptCore/Scripts/generate-js-builtins.py | |
parent | 6d998167b9f14d441172022636091251fa34a15a (diff) | |
download | qtwebkit-05ea746d3042d1409305bc1ebcaf15095870b6d9.tar.gz |
Integrate QWebChannel with QtWebKit.
WebView.experimental gets a new webChannel property. By default, this
is initialized to a QQmlWebChannel internal to the WebView. By setting
it from the outside, it is possible to share the same WebChannel
between different WebViews. The webChannel property can be set to null
to disable this new feature.
For IPC, a navigator.qtWebChannelTransport property is added, which is
essentially a copy of navigator.qt. This is required to be able to use
both independently. The transport is implicitly connected to the
WebView's webChannel.
On the JavaScript client side, some manual boiler plate code is still
required. Potentially, this can be adapted in the future to preload
the qwebchannel.js. Furthermore, we might be able to instantiate and
initialize the QWebChannel before we emit window.onload.
A basic test is added which verifies that this basic integration works.
Change-Id: I5eb0389e6edd6d0c978917e441365e11a02b5c3f
Reviewed-by: Milian Wolff <milian.wolff@kdab.com>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@digia.com>
Diffstat (limited to 'Source/JavaScriptCore/Scripts/generate-js-builtins.py')
0 files changed, 0 insertions, 0 deletions