| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Pick-to: 6.2
Change-Id: I04c6f3f6bdfadcddac6d79440d6e292241bc50cd
Reviewed-by: Christian Strømme <christian.stromme@qt.io>
|
| |
|
|
|
|
| |
Task-number: QTBUG-75722
Change-Id: I78535572f360ada21d1d1f44e1aeacd32dafb2c0
Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the hard build dependency to QtWebEngine, which opens up
the possibility for QtWebEngine, or others, to provide their own plugin.
Another benefit of having the backends loaded at run-time, is that we
can provide an alternative for developers that wants to publish their
application in the App Store, where shipping QtWebEngine isn't an option,
due to store policies, and where we already have an alternative/experimental
backend that can be used.
[ChangeLog][WebView] QtWebView will now load its backends at run-time.
Task-number: QTBUG-63137
Change-Id: I581940fe4c3b5e6bb41896367d3163ac8bc7b6b9
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| |
|
|
|
|
|
|
|
| |
This allows using the WKWebView or WebView backends of QtWebView via the
QT_MAC_USE_NATIVE_WEBVIEW environment variable without having to rebuild
the module with CONFIG+=osx_webview_experimental.
Change-Id: I20b4406af2dadd90d2c2c81b896d20e4b57c9909
Reviewed-by: Christian Stromme <christian.stromme@qt.io>
|
| |
|
|
|
|
|
|
|
| |
don't try to build the example when the library is missing.
also, don't try to build the whole module if it will be entirely empty.
Change-Id: I4de9b6c2454bbfea60dc6b747cd995cfab6c7617
Reviewed-by: Andrew Knight <andrew.knight@intopalo.com>
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com>
|
| |
|
