QtWebEngineRoadMap: Difference between revisions

Latest revision as of 14:11, 18 August 2026

Note: The content of this page has been created in 2016, at the beginning of the project. Today, it does not reflect the current status anymore. This page should be updated, or put offline or moved to an archive

Known/Foreseen use cases

The usual Web Browser stuff (Embedded platforms, KDE…)
Presenting and integrating web contents (Hybrid apps, ported web apps…)
Headless testing and so on (think also SVG rendering/printing to pdf, etc)

Features

Graphical integration, with QtQuick and Widgets, forwarding of events, etc
JS bridge of sort (exposing QObject to the JS context, invoking JS on the web contents side, etc)
Network integration. Unclear how to do it and to what extent it should integrate. Some of the common use cases
- custom schemes
- loading policies
- proxy settings
- cookies
- disk cache
- authentication
- custom CAs

@@ Line 1: / Line 1: @@
-''The project is still young, so we don’t have such a thing as a very clear roadmap, but here are the use cases we’ve identified and features we plan on looking into at one point or another:''
+Note: The content of this page has been created in 2016, at the beginning of the project. Today, it does not reflect the current status anymore. This page should be updated, or put offline or moved to an archive
-==Known/Foreseen use cases==
+== Known/Foreseen use cases ==
-* The usual Web Browser stuff (Embedded platforms, <span class="caps">KDE</span>…)
+* The usual Web Browser stuff (Embedded platforms, KDE…)
 * Presenting and integrating web contents (Hybrid apps, ported web apps…)
-* Headless testing and so on (think also <span class="caps">SVG</span> rendering/printing to pdf, etc)
+* Headless testing and so on (think also SVG rendering/printing to pdf, etc)
-==Features==
+== Features ==
 * Graphical integration, with QtQuick and Widgets, forwarding of events, etc
@@ Line 19: / Line 19: @@
 ** authentication
 ** custom CAs
-* Extending access rights for apps.