[Qtwebengine] Hopeful of a timeline?

David Cortesi davecortesi at gmail.com
Tue Dec 30 02:28:19 CET 2014

I was glad when Qt5.4 was released because I was eager to use QWebEngine.
However when I began to port my app (a simple special-purpose browser) I
was surprised to find some QWebKit features not (yet?) supported. Reading
the archives of this list, it appears I was not the only one surprised --
but surprise would be natural, given statements such as this from the digia
blog (http://blog.qt.digia.com/blog/2014/12/10/qt-5-4-released/)

HTML5 and Web technologies have become more and more important over the
> last years, and we have spent the last year developing a completely renewed
> Web offering for Qt. The Qt WebEngine
> <http://doc.qt.io/qt-5/qtwebengine-index.html> module is the result of a
> long-term R&D project where we adopted the Chromium Web engine for use
> within Qt. With Qt 5.4, it is fully supported on the most used desktop and
> embedded platforms. Qt WebEngine provides you with an easy-to-use API to
> embed Web content in both Qt Widgets and Qt Quick based applications.

Nothing in that announcement suggests that WebEngine is only partially
finished. Indeed, "completely renewed offering" and "fully supported" might
make a person think it is ready to replace WebKit.

Well, that would be a problem of communication from dev. to marketing,
perhaps -- anyway it's water under the bridge!

What I would hope to see happen now is to assemble a list of WebKit
features that are NOT available in WebEngine 5.4, with some indication of
whether each feature is (a) not planned (b) planned but with a different
API (c) planned for 5.5, (d) planned for someday, etc.

Here in no particular order are things that I could not port to WebEngine
in my simple app:

Settings: PluginsEnabled(bool)

Settings: JavaEnabled(bool) -- I suspect in Chromium this is subsumed under

Settings: PrivateBrowsingEnabled(bool) -- Chrome browser definitely
supports it

QWebFrame::hitTestContent(QPosition) -- necessary for a custom context menu
to adapt to "what's clicked"

QWebPage.setContentEditable(bool) -- looks as if currently WebEngine pages
are not editable, could they ever be?

QWebPage.setLinkDelegationPolicy(policy) and the associated
linkClicked(URL) signal.

What else? And is there a timeline, or at least priority list, for these

Thanks for your attention,

Dave Cortesi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20141229/8197bcf9/attachment.html>

More information about the QtWebEngine mailing list