QtWebEngine

@isildursheir Check this post.

@Lee-Coder OK， I fixed this problem. If you have the same problem,maybe this topic can help you. If you import QtQuick.Controls 2.0 or QtWebEngine 1.x, the cmd command "windeployqt xxx.exe --qmldir xxx" can not auto copy required qml folder, you must manual copy qml folder,like this: QtQuick.Controls 2.0 - %you qt path%/5.7/msvc2013_64/qml/QtQuick/Controls.2,copy all folder in your dynamic compiler project,eg:%dynamic compiler project%/QtQuick/Controls.2 QtWebEngine follow the same steps specified above. OK~it's work! thx~

@p3c0 said in Pepper Flash fullscreen and customize ScrollBars in QWebEngineView or QWebEnginePage: scrollbar OK,I know it

Thank you so much! That should do it!

@THEFree Oh! You're Welcome :)

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

I solved.... i am using Cesium Server on MachineA, and i open Cesium on Chromium Browser on MachineB. Js of Cesium in which i create a webchanel to exchange message with standalone exe (qt Webchannel example) must be on the same directory on Machine A. index.html on Machine B (Web Server on Machine A) refer to correct address and port on Machine A and found server qwebchannel on correct location. The post can be closed . Best

Hi and welcome to devnet, This is not the right place to report potential bugs. You should go on the bug report system to see if it's something known. If not please open a new report providing as much information as possible including development environment.

Hi, @Thuan_Firelight I'd recommend posting that question on the QtWebEngine mailing list. You'll find there QtWebEngine developers/maintainers. @Good-Guy Please stop posting such useless comments, they are not useful nor helping @Thuan_Firelight. The reasons for why QtWebKit has been deprecated have already been explained. Since you're not happy with that, then you should take a look at @Konstantin-Tokarev QtWebKit reboot.

@Thuan_Firelight Hi! The first version with full Windows 10 support was Qt 5.6. This is also the latest Long Term Support release, so it's definitely worth upgrading.

just remove the ':' in your scheme name: profile->installUrlSchemeHandler(QByteArray("qthelp"),weush);

Thanks...

Hi I have found that when using in QML WebEngineView component, one should enable in QML the flash plugin as WebEngineView { id: webView anchors.fill: parent url: "http://" Component.onCompleted: { //enable flash plugin webView.settings.pluginsEnabled = true } } Otherwise the instructions above are correct. regards Bogdan

@raven-worx Thx, I will get cracking on this. Much appreciated.

There are two general ways: to use the QtWebKit or the QtWebEngine. There are memory usage and rendering issues with QtWebKit and it is deprecated since Qt 5.5, but its API is synchronous and simplier to use. In case it is possible to use the 5.5 or an older version of Qt with precompiled QWebKit or you are able to build the module for target platform(s) manually (which could be a bit tricky), just try to open target web page in the QWebView (see the demo browser in the examples). If the page is rendered properly, interaction with inputs/buttons is adequate and there are no visible crashes/freezes/memory leaking - you can use the QWebKit :) ... connect( webView->page(), //-- or webView->page()->mainFrame(), depending on the DOM structure SIGNAL(loadFinished(bool), this, SLOT(onWebContentLoaded(bool)); ... void ...::onWebContentLoaded(bool ok) { if(!isLogedIn()) //-- parse HTML to find markers or just check a flag actualized in the doLogIn(); doLogIn(); else extractTheData(); } void ...::doLogIn() { if( QWebFrame *frame = webView->page()->mainFrame() ) { QWebElement inputLogin = frame->findFirstElement( "#user" ); //-- Chrome->View Source (Ctrl+Shift+I)->Copy->Copy Selector QWebElement inputPass = frame->findFirstElement( "#password" ); QWebElement buttonSubmit = frame->findFirstElement( "#login" ); if(!inputLogin.isNull() && !inputPass.isNull() && !buttonSubmit.isNull() ) { inputLogin.setAttribute("value", ui->lineEditLogin->text() ); //-- populate HTML's input via API inputPass.evaluateJavaScript( QString("this.value='%1'").arg( ui->lineEditPass->text())); //-- or via JS buttonSubmit.evaluateJavaScript( "this.click()" ); //-- or you can generate a key/mouse event } } } In case you are forced to use the QWebEngine, things are a bit more complicated: you have to use a QWebChannel to expose your QObject to the JS side, where all interaction/extraction will be done. In both cases to keep alive all routines/events needed for correct page rendering while widget is hidden, set the webView's (or its parent's) attribute Qt::WA_DontShowOnScreen to true.