mark
qtwebengine_resources.pak + qtwebengine_resources_100p.pak+ qtwebengine_resources_200p.pak

In my case this function works:

onFeaturePermissionRequested: { console.log("onFeaturePermissionRequested"); webEngineView.grantFeaturePermission(securityOrigin, feature, true); }

Tested on Qt 5.6 and Qt 5.7 on Desktop and Embedded

Hi,

Did you also install Qt for MSVC2013 ?

Hi and welcome to devnet,

That's a question you should bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

Hi,

I'd recommend posting that question to the the QtWebEngine mailing list. You'll find there QtWebEngine's developers/maintainers. This forum is more user oriented.

Thanks. I take a look at hat and at http://tishion.github.io/QCefView/

But then we end up in using an extra lib. Something we want to avoid.... :-(

I had the same question as you,I think ,maybe your project is short of the '.js' file.
You can add the '.js' file to the project-resource , then have a try.

By the way ,In my project , It has the ',js' file,but there is still a quetion.
In my projtct,I want load a HTML that use google maps api and show maps offline ,oc course I have doemloaded the map titles .the HTML can work in any browser, such as chrome, IE ,firefox and so on,but the html doesnot work in Qt5.6.0 which I use the QWebEngineWidget class.
The error is :
js: Uncaught TypeError:google.maps.LatLng is not a function
js: Uncaught TypeError:google.maps.MAP is not a function

So,this is my question,I haven't solved。

Solved: the cause was the stub in mesa3d drm backend. It's solved by altering the backend.

Old post but I had the same error; I had to build qtdeclarative BEFORE qwebchannel to solve this error.

@Zevero I had the same problem, is there a solution for the mouse click that doesn't work in the web pages.

alas no luck - so far still the only option is to use command line parameters to your own app - and yes every single embedded web engine sub-process will reuse the same parameters (no luck with different proxy per tab problem)
e.g. if you try
MyApp.exe --proxy-server=host:port
and your app opens 10 tabs the same proxy it will be reused by every single tab/or browser/or sub-process/
pretty much the same as setting global proxy (at application level)

https://bugreports.qt.io/browse/QTBUG-59490

BTW: if they implement the above they need to decide which has higher priority - global app level proxy or per web engine sub-process

Hi

May I ask how you got this to build?

I am trying to compile Qt with the following configuration (for Raspberry Pi):

./configure --prefix=/usr -release -opensource -confirm-license -c++11 -no-largefile -no-qml-debug -system-zlib \ -no-journald -system-libpng -system-freetype -system-libjpeg -system-sqlite -openssl -no-pulseaudio -alsa \ -no-sql-db2 -no-sql-ibase -no-sql-mysql -no-sql-oci -no-sql-odbc -no-sql-psql -no-sql-sqlite2 -no-sql-tds -nomake examples -reduce-exports \ -no-directfb -no-linuxfb -eglfs -no-xcb -device linux-rasp-pi-g++ -device-option CROSS_COMPILE=/usr/bin/ -sysroot /

Here is my patch:

diff --git a/qtwebengine/tools/qmake/mkspecs/features/functions.prf b/qtwebengine/tools/qmake/mkspecs/features/functions.prf index ef0320d..5abaecc 100644 --- a/qtwebengine/tools/qmake/mkspecs/features/functions.prf +++ b/qtwebengine/tools/qmake/mkspecs/features/functions.prf @@ -12,13 +12,9 @@ defineTest(isPlatformSupported) { return(false) } - linux-g++*:!isGCCVersionSupported(): return(false) - !isPythonVersionSupported(): return(false) - linux-g++*|win32-msvc2013|macx-clang: return(true) boot2qt: return(true) - skipBuild("Qt WebEngine can currently only be built for Linux (GCC), Windows (MSVC 2013), OS X (XCode 5.1+) or Qt for Device Creation.") - return(false) + return(true) } defineTest(isPythonVersionSupported) { -- 2.1.0

And it succeeds, but I don't get a message about WebEngine being an unsupported platform. It simply does not build that module. I tried to follow this reference here, but had no luck either: https://forum.qt.io/topic/48223/webengine-raspberry-pi/2

I am building native, not cross, on Debian Jessie.

Thanks in advance,

Sam

Waiting online~~~

Well, it was caused by a QGraphicsEffect on the QWidget.
After removing it, the QWebEngineView worked without any flaws. weird.