[Development] QtWebEngine (was: Re: Clarification needed for Qt Script's future over QJSEngine/Value)

Kevin Kofler kevin.kofler at chello.at
Sun Nov 30 06:33:58 CET 2014

Lisandro Damián Nicanor Pérez Meyer wrote:
> Which means that lots of archs will not be able to have QtWebEngine.

Right. This is one of the many problems of QtWebEngine and its Chromium 
dependency. (It will affect the Fedora secondary architectures, too.)

If you want to know the others:
* bundling of Chromium by QtWebEngine,
* bundling of many libraries by Chromium (and thus transitively by
* lack of integration with the system and even Qt itself, e.g.:
  - we lose QNetworkAccess, which allowed making QtWebKit use KIO (see
    KWebKitPart) – Chromium hardcodes its network access code instead. This
    also means no support for man:, info:, gopher: etc. protocols, unless
    they get implemented as Chromium plugins (but last I checked,
    QtWebEngine also didn't support those).
  - no GStreamer support. (Direct FFmpeg use is a PITA for distributions to
    deal with.)

We are not even sure we will be able to import QtWebEngine into Fedora at 
all, because of the bundling and FFmpeg issues. (So far, nobody has dared 
even trying to submit it for review.)

        Kevin Kofler

More information about the Development mailing list