Skip to content

QtWebEngine

Discussions and questions on QtWebEngine
1.3k Topics 3.8k Posts
  • 0 Votes
    2 Posts
    1k Views
    D

    Here are the screenshots depicting the problem:
    works from web
    fails from local drive

  • WebGL

    2
    0 Votes
    2 Posts
    3k Views
    K

    Just an FYI, disabling network adapters (used by virtual machines) in Device Manager solved the sluggishness for me.

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    1 Posts
    649 Views
    No one has replied
  • 0 Votes
    2 Posts
    2k Views
    A

    Hi Rahul,

    I am looking something similar i.e. logs of Qt framework. Refer https://forum.qt.io/topic/58566/how-to-print-logs-qdebug-qwarning-qcritical-qfatal-of-qt-framework-libraries-itself

    Try using --log-level=0. It might work in your case.

    Thanks,
    Anant Agrawal

  • Access to a QWebElement

    6
    0 Votes
    6 Posts
    2k Views
    M

    have you tried a simple alert from your Qt to Js?

    QString jsCode = "alert('helloWorld');"; ui->webView_studio->page()->mainFrame()->documentElement().evaluateJavaScript(jsCode + "; null");

    if this works then the problem is the syntax of your javascript inside Qt.

  • 0 Votes
    5 Posts
    2k Views
    O

    @p3c0 That worked, thanks for your help.

  • QtWebEngine & HTML5 Application Cache

    2
    0 Votes
    2 Posts
    5k Views
    J

    Hi,

    Now you can use the following line for a QWebEngineView object :

    webview ->page()->profile()->setCachePath("C:/Users/yourUserName/AppCacheFolder");

    See you.

  • Webelement click does not work

    14
    0 Votes
    14 Posts
    7k Views
    M

    evaluateJavaScript is your friend

    Exemple of code working with Jquery, replace with javascript code

    QString jsToExecute += "$('#login-btn').click(); "; ui->webView_login->page()->mainFrame()->documentElement().evaluateJavaScript(jsToExecute + "; null" );
  • 0 Votes
    5 Posts
    5k Views
    H

    Disregard my previous post, cookies policy can be set in the QWebEngineProfile owned by the QWebEnginePage owned by the QWebEngineView, like this: ui->webView->page()->profile()->setPersistentCookiesPolicy(QWebEngineProfile::NoPersistentCookies);

    The page pointer remains the same for my purposes, at least.

  • 0 Votes
    2 Posts
    1k Views
    SGaistS

    Hi and welcome to devnet,

    If you can reproduce this easily with a minimal compilable example, you should go to the bug report system to see if it's something known. If not please consider opening a new report providing that example and the guidelines to trigger the bug.

  • 0 Votes
    3 Posts
    9k Views
    MeerMusikM

    Hello.

    I just did a Test Deploy on a Windows 10 and a Windows 7 Clean VM Machine. Qt Version is 5.5.0

    I know this is about Embedded Linux and around 5 Months old.
    But I have the same Problem. It is exactly the same Error Message. Does anybody found a real working Solution yet? The .pak File is in my Application Main Folder. I created a qt.conf and tried the following Settings:

    [Paths] Prefix=<QCoreApplication::applicationDirPath()> Prefix=<> Prefix=<\> Prefix=<&PWD>

    Nothing worked so far. I could not find the answer, how to tell Prefix to use the current Directory.
    In addition: Has anybody created a BR yet? If not, I can do this.

    Thanks
    Oliver

    EDIT01: Finally I found a way to make it work:

    [Paths] Prefix=.

    Time will tell if this will bring up other Bugs, Glitches etc.

  • This topic is deleted!

    Locked
    2
    0 Votes
    2 Posts
    61 Views
  • 0 Votes
    7 Posts
    6k Views
    N

    OK, so I just tried it again and now it works. No idea what's different from earlier this week, but I'm glad it works now. :]

  • 0 Votes
    2 Posts
    1k Views
    DuinoD

    Waiting online~~~

  • Windows 10 and MSVC 2015 RTM: Known Workaround?

    Solved
    3
    0 Votes
    3 Posts
    2k Views
    MeerMusikM

    Hello.

    Yesterday I have tried the following and failed:

    I have changed the Part from Line 1 in File '..\qtwebengine\tools\qmake\mkspecs\features\functions.prf'
    from:

    !win32-msvc2013: !contains(QT_CONFIG, c++11) {

    To:

    !win32-msvc2015: !contains(QT_CONFIG, c++11) {

    And in Line 17 from:

    linux-g++*|win32-msvc2013|macx-clang: return(true)

    To:

    linux-g++*|win32-msvc2013|win32-msvc2015|macx-clang: return(true)

    As I am absolutely new to QtWebEngine, I am not sure If this is enough. But after I found an Entry at code.qt.io from Michael BrĂ¼ning called "Print a more descriptive warning when a build is skipped.", I thought I would give it a try.

    The Result is the following Error:

    Using extra options found in c:\qt5src\qtwebengine\src\core\qtwebengine_extras.gypi Traceback (most recent call last): File "C:/qt5src/qtwebengine/tools/buildscripts/gyp_qtwebengine", line 147, in <module> args.extend(['-Goutput_dir='+ os.path.relpath(output_dir, qtwebengine_root)]) File "C:\Python32\lib\ntpath.py", line 528, in relpath % (path_prefix, start_prefix)) ValueError: path is on drive D:, start on drive c: Project ERROR: -- running gyp_qtwebengine failed -- NMAKE : fatal error U1077: '(' : return code '0x3' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop. NMAKE : fatal error U1077: 'cd' : return code '0x2' Stop.

    ['Python32' is Python 32-bit but it contains the latest Python 2.7 Package. Bad old naming leftover.]
    I dont know enough about QtWebEngine and nearly nothing about Python. I have to wait for a fix from someone who knows what (s)he's doing. My Bug Report has set to P2 - so with any luck, this will be fixed in 5.5.1

    Until then I have to work with a pre-built MSVC 2013 Package. My Tool is far from ready to be released. So I still have time to wait for a fix for WebEngine and and a fix for ICU as well.

    Have a sunny weekend everyone :)
    Thanks
    Oliver

  • 1 Votes
    1 Posts
    827 Views
    No one has replied
  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • QT Vs RPC JSON 2.0

    1
    0 Votes
    1 Posts
    2k Views
    No one has replied
  • 0 Votes
    2 Posts
    3k Views
    D

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