Fix tst_QWebEngineView::crashTests test case

This test runs without crash, but fails because the expected
interval of the load progress is too narrow.

For example, the progress values in my case: 0 -> 10 -> 100

Change-Id: I0fd13d6badf717fc27e8d4219f39190db0090692
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Replace uses of QWebEngineFrame with a security origin URL

This changes implemented methods. The rest of the references will go
away with the public headers cleanup.

Change-Id: I82340cd7a4488c4b463489ae98cd9c16de4e7487
Reviewed-by: Michael Bruning <michael.bruning@digia.com>
Cleanup the QtWebEngineWidgets public headers and API

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>
Windows: Use the runtime library the same way as Qt

Using a custom allocator prevents us from allocating memory in Chromium
cc files and freeing it in our code. Always use the normal CRT heap
allocator to allow this.

This also makes sure that we use the same /M flags for Chromium
translation units as for Qt when dynamically linked. We won't support
statically linking QtWebEngine at first anyway.

Change-Id: Ifa044c7d3cf39929f7e4ca1c4c4cb3a9dea96266
Reviewed-by: Michael Bruning <michael.bruning@digia.com>
Windows: Fix a crash in ContentMainRunnerImpl::Initialize

It will try to dereference the SandboxInterfaceInfo* that we pass it.
Fix the issue by creating a dummy instance on the stack when calling
it.

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