Qt-contributors-summit-2014-Qt-WebEngine-Qt-WebKit

This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.

Qt WebEngine / Qt WebKit

Past:

• There has been about a year to come to a point where we are ready to replace QtWebKit
• More complex features like the JS bridge are planned to be covered by the QtWebChannel
• Support for Windows to be added for Qt 5.4
• Linux support is stable, Mac works but can have issues

Future:

• Bring feature parity is on the way, with some exceptions

General discussion:

• Need to more aggressively make proven experimental APIs public
• Memory overhead of QtWebEngine compared to QtWebKit vs. the reliability gain
• Process of updating Chromium: the lower difficulty allows updating more often
• SSL certificates exceptions, if the application needs to take care of it, and the need to make that process asynchronous in the user interface

Wished features discussion:

• Controls over the cookie jar and used proxy settings