|
|
| Line 1: |
Line 1: |
| =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 <span class="caps">API</span>s public
| |
| * Memory overhead of QtWebEngine compared to QtWebKit vs. the reliability gain
| |
| * Process of updating Chromium: the lower difficulty allows updating more often
| |
| * <span class="caps">SSL</span> 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
| |