Check properly for EGL extensions before using them

Always check both EGL_EXTENSIONS and the validity of the returned
function pointers. Otherwise bad things happen on EGL implementations
that do not have the extension.

Fix also linking to EGL. CONFIG+=egl has to be in core_module.pro too.

Change-Id: I5e3dc54675d83123fc79e2d27a7af19fcc7f936a
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Fix up some more documentation.

Removes methods from the documentation that no longer exist.

Removes left over instance of Qt WebKit / WebKit instead of
Qt WebEngine / Chromium in the documentation.

Change-Id: I27e1d41fc16116a60f94c3369f76ddfed60e4380
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Remove the xPath argument from runJavaScript

This value is only used internally by Chromium and risks being removed
at anytime, for which we would then have to maintain a downstream
implementation.

Chromium also only supports frame values, while a complete support of
the interface would require also supporting this xPath to point to
individual document element by affecting the value of "this", the same
way that QWebElement::evaluateJavaScript allowed in QtWebKit.

Change-Id: Id0cb1b8e3bdf9a6db0ca786fb5eb46ffd726d165
Reviewed-by: Michael Bruning <michael.bruning@digia.com>
Fix the Chromium upstream initialization on Windows.

The Windows git version is not able to check out some extra_os
dependencies but since they are not relevant on Windows
we can just skip them.

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