Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Chromedriver support in Qt 5.12?
Forum Updated to NodeBB v4.3 + New Features

Chromedriver support in Qt 5.12?

Scheduled Pinned Locked Moved Solved QtWebEngine
3 Posts 2 Posters 1.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    dfaber1
    wrote on last edited by dfaber1
    #1

    I am attempting to build chromedriver for the QtWebEngine as part of Qt5.12, which is based on Chromium 69.0.3497.128. QtWebEngine is successfully cross-compiled for 32bit embedded Linux target. No chromedriver is built as part of this build however. I cannot find any details on how to enable it or if it is supported in Qt5.12, or if it plans to be supported in the future.

    Looking at the source, I can see chromedriver in the QtWebEngine source (qtwebengine/src/3rdparty/chromium/chrome/test/chromedriver), however it is just a mostly empty directory with a BUILD.gn file. Looking at the Chromium project at 69.0.3497.128 there is a full source for chromedriver (https://github.com/chromium/chromium/tree/69.0.3497.128/chrome/test/chromedriver).

    Attempts at dropping this source into the QtWebEngine tree do not yield it being automatically picked up to be built. Attempting to use the QtWebEngine gn/ninja tools to build the Chromium chromedriver source does not seem to be directly supported either.

    Is there a Qt supported approach to including chromedriver (or any webdriver implementation) in the QtWebEngine build?

    1 Reply Last reply
    0
    • A Offline
      A Offline
      Allan Jensen
      wrote on last edited by
      #2

      No the code is stripped out of our build. That is why the dir is mostly empty (we need to leave the BUILD.gn file in there, because GN is a terrible build system which deals poorly unused code pointing at nonexisting parts)

      D 1 Reply Last reply
      0
      • A Allan Jensen

        No the code is stripped out of our build. That is why the dir is mostly empty (we need to leave the BUILD.gn file in there, because GN is a terrible build system which deals poorly unused code pointing at nonexisting parts)

        D Offline
        D Offline
        dfaber1
        wrote on last edited by dfaber1
        #3

        @Allan-Jensen thanks for the clarification (completely agree about gn). Is there a recommended approach for supporting a webdriver implementation for QtWebEngine?

        Edit to rephrase so it doesn't seem like I am just re-asking the same question again :
        Was chromedriver removed for a specific reason? I.e. if I tried to add it back in would I expect to run into the problems that led to it being removed in the first place? Is it expected that a chromedriver built from upstream Chromium project be compatible with the Qt fork for QtWebEngine? Does Qt have a different test interface that would replace the need for a webdriver implementation?

        Feature request tracked here:
        https://bugreports.qt.io/browse/QTBUG-82046

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved