Fixing unused parameter warnings.
Change-Id: Ic4b60b85f2434aa745e1aeb412984dc3f8a62820
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>

Change-Id: I2d9f23a9aa8871df7b3054628a2db49ea858c522
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@digia.com>

- Fix the example pages titles to match the qdocconf files
- Remove information not as relevant for QtWebEngine as it was for
  QtWebKit
- Fix the QtWebEngineWidgets snippet not to refer to webengine
- Remove the dead link and the reference to Arora from QtWebEngine

Change-Id: Ib3c57c8dd534330b3323c94fb2217374b3e52cf9
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

The unified toolbar doesn't work yet with QOpenGLWidget, which we use
to render RenderWidgetHostViewQtDelegateWidget.

Task-number: QTBUG-41179
Change-Id: I5b33d8c06600162974a05bff5fec6e1c7b59e939
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This test fails, because we get two loadProgress signals with
the 100 value if the page load is successful.

Change-Id: Idbd68c28ba81f8ff0a5b1d98aece82e7a940f1b9
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This adds API for overriding some certificate errors. Once overridden
any identical error for the same hostname and certificate will use
the same override.

Similar API for QtWebEngine QML should be added in a later patch.

Change-Id: I144147b86d9b592e3f87346a1e48890acee0c670
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Change-Id: I7dc7261aadbbf08dbbeb1323cf46d24dc8e58e16
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

We now have the QWebEngineSettings class and can re-enable the features
that were previously disabled in the browser that depended on it.

Change-Id: I525dd1a4b5c380ad4c6060f276440e069f633897
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

AddNewContents is only called when window.open is called from JavaScript.

We also want the shift/ctrl modifiers to trigger normal links to open
in the requested disposition. In this case OpenURLFromTab will pass
the detected disposition and we must create a new WebContents
ourselves.

Use the same code path going through
WebContentsAdapterClient::adoptNewWindow except that we pass a null
WebContents pointer to the WebContentsAdapter constructor and let it
create its own when initialized.

Change-Id: I817b0e72aec12723bf92d9b7ad85c1cecbf5e408
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

To allow the qt5.git integration, allow the build to succeed if the
repository is checked out on a platform that we don't maintain.

This is the initial list of platforms that we want the integration
to succeed and we can add new ones once we start maintaining them.

Change-Id: Idce2a84eb8d5b1ef7f14d399fe013f666b479108
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Also update all the examples to use 1.0 as 0.9 shouldn't be
publically recommended.

Change-Id: Ic58e35bdfd3a0f3d5201fc069b7103027ba84574
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

and make it a namespace

Change-Id: I15c1af8c7d0d8ab213cdf7945109263fe461d2ac
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

If we consider the plugin scenario is unlikely and decide it's
unsupported for widgets, we can simplify our tests and examples
a bit on this front.

Change-Id: Idc96032c127b4ee74fb5c7b3d2cdfdf99c3a722e
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

We actually already depend on dev (5.4) in other areas.

Change-Id: Iab297a51ab06209a96f11f97c74463d38203eda8
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Adds one of the missing pieces of the QWebFrame and QWebView APIs.
Unlike the QtWebKit version this only fetches the favicon URL, and not
the icon. This is because we do not want to implement an icon database,
and that the icon would be loaded asynchronous anyway, bringing no
guarantee to be a valid icon/image yet.

Change-Id: I227311ae3676044da850e687b82bee752b5079c8
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Change-Id: Icc4219ace4121a4b30302e0348e48dc75cae54cb
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

Change-Id: Icecb6b716a45b4682ddd9b16383f3aa4a5acb312
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Change-Id: Ia1a92a7eb9b3568e8cb7ccf6c7056abba647fd8d
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

Change-Id: Ib1d855bab6c764c0341b39b374b00425645903ff
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: If2ac075f095c83fd53c939d3494c7807328ed2dc
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Drop hovered title and link text parameters, as we did
in the Quick API.

Change-Id: Ia1a38e0d728afbcbb6858a890486772da74aa813
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

I dropped hovered title support from the QtWebKit API,
it seems we don't need that logic.

Change-Id: I5617c295344512a35aa526a6f1307f0b21f866d6
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Change-Id: Ib2deac6099c37f1e112821fb3398586269e05f22
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

Headers were left intact to leave a trace of the evolution compared
to the QtWebKit API and to make it easier to work until we had a
basic subset of the API implemented.

With the upcoming release, this patch removes this convenience in the
aim of starting polishing the headers and the documentation for the
upcoming release.

Change-Id: Iae436b4ec041d771a7002575e122835802bc9f3e
Reviewed-by: Michael Bruning <michael.bruning@digia.com>

Expose the same values as currently available in
QQuickWebEngineView::NewViewDestination.

Rename the WebModalDialog to WebDialog, which actually replaces the
tool/status/menuBarVisibilityChangeRequested signals.

Change-Id: Icc103f434fb3eca49f1a53e476e101c3d6fffd36
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Change-Id: I8a805feb1893f2e4b08944e2fc987d0a8fbbc89a
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

This means that widgets application now need to setup the GL context
sharing as well. QWebEngineWidgets::initialize() must be called,
which has the same effect as QWebEngine::initialize().
The QtWebEngineWidgets now depends on the QtWebEngine module to make
this happen.

Since QOpenGLWidget is only available in Qt 5.3, this patch also
disables the webenginewidgets module completely when building using
Qt 5.2.

Change-Id: I0e99a779d1eb080f2ccf5a338ff0763ad64e6eba
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

We now require the user to use QWebEngine::initialize() in main (preferably) and
print out an error message if this wasn't set up accordingly. This limits the use
of private scene graph API to inside QWebEngine and offers public API for users
of the API.

Change-Id: I787c176a85ab7784dbc8787d9876960b4872959e
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>

This is a gross mechanical modification of the documentation, along with build
system bindings to allow it to generate. This should allow doing iterative
improvements to the documentation from now on.

This fixes project-related qdoc warnings but we still need to do some serious
work to get the documentation better fitting QtWebEngine. All the documentation
is ported to match the current state of our headers (without trying to adapt
to modified APIs yet) and we should clear the part of the documentation that we
don't need at the same time that we clean up our public headers.

Change-Id: I6fb4e10e8b4c1c53be7bc7c581286248ac04d4da
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

Remove ContextMenuExtras.qml entry from the project file
of the quicknanobrowser. It is unnecessary after the quicknanobrowser
fork.

Change-Id: I87055413392e14817429678f29b520e55cafbbd1
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

This also removed experimental API uses from the quicknanobrowser example,
which should be used mainly for documentation purposes.

The quicktestbrowser should be the one that we use from now on as a raw testbed
of new APIs.

As with other targets in the tests directory, it will only be built by default
if Qt is configured with -developer-build (and without -nomake tests).

Change-Id: Ib4461c898cd3227bbb810493daac4d841d0d8f3e
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

Its sources are going to be installed and the binary should end up at the same
place.

Change-Id: Iad7c732ba9f49cb0f02eb2c10b797298034ef38d
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

To match other modules example directory structures we should deploy our
examples in a directory matching the module name, webengine and
webenginewidgets in our case.

qmake uses the relative directory of each example up to the upper "examples"
directory to decide where they will be deployed when running the sources
install target.

Change-Id: I59ce7ff8a30f98fad20064c7eecf72b784f1d275
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

This example hasn't been touched since we imported QtWebKit examples.
If we need to have a more test-purpose widgets browser in the future,
we can dig it back from the history.

Change-Id: Icee9bd7f09827a97b33c6783b87311e331d963b1
Reviewed-by: Pierre Rossi <pierre.rossi@gmail.com>

The tabs.currentView property was probably removed in some earlier
change and is undefined, use the currentWebView property instead.

Change-Id: I0fc31b0cc7191f2ed2f57c27306387f062cff2e1
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>

This allows handling calls that would be signaled by QNetworkAccessManager
in QtWebKit.
This pulls QtNetwork as a dependency of the QtWebEngineWidgets module
to be able to use QAuthenticator, but isn't required otherwise.

Only the request URL is available in the case of HTTP authentication
(no access to HTTP request headers that the QNetworkReply would allow)
and only the proxy host name in the case case of proxy authentication.

This keeps the API synchronous the same way, as QtWebKit did, in
favor of source compatibility at the cost of requiring a modal
dialog, even though the implementation doesn't require it.

Change-Id: I9e021def38e6107c9e66d2de8f86bd0328d543df
Reviewed-by: Michael Bruning <michael.bruning@digia.com>

Cleanup version ifdefs and v8-private dependencies.

Change-Id: Iac393c06dfba02499e60d713d9f4d04ef0c9e617
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>

A few changes to the API:
- Return the success result asynchronously.
- FindWrapsAroundDocument and HighlightAllOccurrences are enabled by
  defaults and cannot be disabled.
- Found text isn't updating the selection on the page like QtWebKit
  did, but triggers a separate state not available. A find count and
  current index could be exposed, but isn't in this case to keep the
  API delta lower.

This also adds the possibility to pass bool results through the
CallbackDirectory and add a new tst_QWebEnginePage::findTextResult
test since the old test relied on the selection to be updated when
the searched text is found.

Change-Id: I8189b5aea8d832df183c6c1ae03e3f08198a9c45
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

Forcing that arguments to be const references isn't necessary and
prevents base types to be passed by value.

Change-Id: I53ace8cf731ecaeee0b997af72d37843ef54e38f
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>

Improve the code and API in a few ways:
- Expose a more discoverable "request" argument in the signal.
- Use the request as the carrier of the backend WebContentsAdapter
  and get rid of our handle.
- Put the adoption method (renamed to openIn) on the request object
  and keep the view API clean of a context-specific adoptHandle method.
- Use an enum instead of strings for the new view destination.
- Do not let JavaScript own the request object since it won't be
  necessary until we want to support asynchronous view attachment.
  We can create the request object on the heap and let the JavaScript
  engine own the object once we want to support it.
- Move the request class to its own header.
- Replace tabs.currentView by currentWebView in the quicknanobrowser
  qml code since we now need this property on the root object anyway.

Change-Id: I40d7d15255f516ead9f3e414dd587bf345e6ca4b
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>