summaryrefslogtreecommitdiffstats
path: root/src/webview/qtwebviewfunctions.cpp
Commit message (Collapse)AuthorAgeFilesLines
* CRA mark src/Moss Heim2025-10-091-0/+1
| | | | | | | | | Some winrt plugin functions do data parsing but since this plugin is defunct, it is still marked with default security level. Fixes: QTBUG-135784 Change-Id: I99739cc762b1801fee65df7e08be17443cad157d Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Do not initialize webenginequickMichal Klocek2025-09-051-6/+0
| | | | | | | | | | | | | The WGL backend is gone, we use DX11, so no more opengl texture sharing setup. This is band-aid patch, docs will be updated later. (if other webview backends do not need initialize) Fixes: QTBUG-139717 Pick-to: 6.10 Change-Id: Id37bdc1e70c8b793959589bfced42096dbe4c939 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* windows: Fix freeze when loading Qt Web Engine pluginEskil Abrahamsen Blomfeldt2024-03-041-0/+6
| | | | | | | | | | | | | | | | | | The mechanism which initializes Qt Web Engine via the plugin loader does not work on some graphics drivers on Windows, which do not support initializing graphics in DllMain(). Since Qt Web Engine is always the backend on Windows, this patch makes Qt Web View depend on it directly and calls initialize from QtWebView::initialize() instead on that platform. [ChangeLog][Windows] Fixed a freeze on startup on Windows. As part of the solution for this, the Qt Web View library now depends directly on Qt Web Engine on Windows, instead of indirectly via the plugin library. Fixes: QTBUG-117882 Change-Id: Ia1b3e54145477f645bbb97856bdbbb68b58d2785 Reviewed-by: Christian Strømme <christian.stromme@qt.io>
* Use SPDX license identifiersLucie Gérard2022-06-101-38/+2
| | | | | | | | | | | Replace the current license disclaimer in files by a SPDX-License-Identifier. License files are organized under LICENSES directory. Pick-to: 6.4 Task-number: QTBUG-67283 Change-Id: I0f719de9e6e1fd4a7c50a247831e5a768e08df14 Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
* Use up-to date LGPL license headerKai Köhne2022-02-141-11/+14
| | | | | | | | | | | | | Remove usages of outdated LGPL3 header that references LICENSES.LGPLv3 instead of LICENSES.LGPL3. Use BSD instead in the examples, updated LGPL otherwise. Also remove the now unreferenced LICENSE.LGPLv3, LICENSE.GPLv2 files, and instead the newly referenced files instead. Pick-to: 6.2 6.3 Change-Id: I01e1325ee2c7a147e095c08b370b88ded9a8daff Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
* Doc: Fix documentation warnings for Qt WebViewTopi Reinio2021-09-171-1/+0
| | | | | | | | | | | | | * Comment out \instantiates link to a private class as we cannot link to it. * Move \qtcmakepackage to the correct place under \module. * Add missing documentation dependencies. Pick-to: 6.2 6.2.0 Fixes: QTBUG-96294 Change-Id: Ib114b6891e050559914049fd944397d34a70f5fa Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io> Reviewed-by: Paul Wicking <paul.wicking@qt.io>
* Clean up Qt WebView documentation for 6.2Christian Strømme2021-09-101-0/+1
| | | | | | | | | | | | | - Added "Using The Module" section that documents how to include the module in CMake. - Removed version numbers from documentation. - Added CMake import section in the QtWebView namespace documentation. - Removed references to UWP. Pick-to: 6.2 6.2.0 Fixes: QTBUG-94935 Change-Id: If5c1f63179506b03653fcbbcbb3bdce5951cce3a Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Update dependencies.yamlAllan Sandfeld Jensen2021-02-041-0/+2
| | | | | Change-Id: Ie4ac89ec6d2ec2c10ff89cd11a46a1271b837170 Reviewed-by: Andy Shaw <andy.shaw@qt.io>
* Do the pre-initialization steps after the plugin paths are setAndy Shaw2021-01-121-9/+25
| | | | | | | | | | | | | Since initialize() is called before the creation of the application then we need to delay the actual implementation until the paths are set. Therefore a prehook is used for the application object so that these can be done before the application finishes initalizing. For static builds we call this function right away, thus requiring the need for the QtWebView::initialize() function to still exist. Pick-to: 5.15 Change-Id: Ic4633cd1e96c39bc12f475fdd22c56646ea7ca10 Reviewed-by: Christian Strømme <christian.stromme@qt.io>
* Make sure that we have a valid plugin before using itChristian Strømme2019-02-261-2/+5
| | | | | | | | | | | | The code assumed that loading the plugin would succeed if we could read its meta-data, this is of course not always the case, as a plugin might not have its dependencies met and fail to load, e.g., this is the case if trying to use the QtWebEngine plugin when QtWebEngine isn't installed. Fixes: QTBUG-71380 Change-Id: Ib88281b2b291213891cfbb77b0728c1bdd6dd1fd Reviewed-by: Kai Koehne <kai.koehne@qt.io>
* Make QtWebView plugin basedChristian Stromme2018-01-261-34/+7
| | | | | | | | | | | | | | | | 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>
* Remove WebView and UIWebView backendsJake Petroules2017-01-111-1/+1
| | | | | | | | Our minimum deployment target is now macOS 10.10 and iOS 8.0 in Qt 5.9, so the WKWebView backend will always be used instead. Change-Id: Ifd24948954cc273fee458c212b1801dc4a5aca45 Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@qt.io>
* Select macOS backend at runtimeJake Petroules2016-07-061-6/+24
| | | | | | | | | 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>
* Doc: Make documentation for QtWebView::initialize() visible.Topi Reinio2015-10-281-0/+1
| | | | | | | | | | Document the QtWebView module, add the Q_WEBVIEW_EXPORT macro to .qdocconf, edit the help project sections and link to the C++ module documentation from the overview. Change-Id: I3deb34e8067278915610e24a15baf52e365629fb Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com> Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
* Use Qt WebEngine by default on OS X.Christian Strømme2015-09-241-1/+1
| | | | | | | | | | This change reverts back to using Qt WebEngine as a backend on OS X, as there are still challenges that needs to be solved when using the native WebView implementation, e.g., make it possible to use it without disabling batched rendering. Change-Id: I9cc95233990055d59480ad4d47ebf3da4ebb07f1 Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
* Add missing header in qtwebviewfunctions.v5.6.0-alpha1Christian Strømme2015-08-281-0/+4
| | | | | | | | We need to include the header for QByteArray, as it's required when calling qputenv(). Change-Id: I245d769b050525719dc6db202a6724ce887ba4a7 Reviewed-by: Yoann Lopes <yoann.lopes@theqtcompany.com>
* Fixed bugs in license headerJani Heikkinen2015-08-251-9/+9
| | | | | | | | | Two files were using old LGPL license headers and that's why license header tests were failed. Changed those files to use LGPLv3 header template Change-Id: I95bd010087b83c6aa174d53e7c2378bdd9e57c70 Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
* Add initialize functionChristian Strømme2015-08-101-0/+74
The initialization function will set-up any platform specific requirements needed to display the WebView correctly. Initially we tried to avoid this, as it's not a very nice approach, and it was only needed when QtWebEngine back-end was the used (see: QtWebEngine::initialize()). Since we now require special set-up for OS X as well, it has become unreasonable to expect that the user should implement this logic in their application and that it's more convenient if we provide a uniform solution to make the WebView work on all platforms. The implication of this change, is that we now actually expose a C++ API and will therefore need to export the module again (making it a non-internal module). Change-Id: I87678db7cd50b25465bcf623c008f04a4cffd7df Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>