summaryrefslogtreecommitdiffstats
path: root/src/core/profile_adapter.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Fix typos in coreMarcell Brauner2025-10-091-1/+1
| | | | | | | Pick-to: 6.10 6.9 6.8 Change-Id: Ia8375615ade18fa1fea3bb42fb6dc560398166d3 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Kaloyan Chehlarski <kaloyan.chehlarski@qt.io>
* CRA mark src/core [4/6]Kaloyan Chehlarski2025-09-251-0/+1
| | | | | | | | QUIP: 23 Fixes: QTBUG-138729 Pick-to: 6.10 6.9 6.8 Change-Id: If91f79fe9d2f8ef7278c99794ea74bc0ceb71d1e Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix -no-ssl buildPeter Varga2025-09-171-9/+19
| | | | | | | | Amends 671afae06 Add API for providing additional CA certificates Pick-to: 6.10 Change-Id: I7e40b9b24e319e89c94d13516ebbc896c8ba6f69 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Associate permissions with framesKaloyan Chehlarski2025-08-201-4/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously, permisions were associated with the originating WebContents, as the PermissionManager API uses those in its function calls. This is insufficient, however, as it results in iframes not receiving the correct permissions (because they were instead granted to the root frame instead. This change modifies the internals of PermissionManagerQt to use GlobalRenderFrameHostTokens, and modifies relevant functions across the codebase to pass those around instead of WebContents. Media and mouse lock permissions now also query the permission manager before issuing a request, which avoids some cases of the same request being sent multiple times in a row. As a side effect, the behavior of non-persistent permissions (as well as the behavior of ALL permissions when running in AskEveryTime mode) is standardized so that a permission is remembered as long as the associated frame is alive. Fixes: QTBUG-134637 Fixes: QTBUG-135787 Pick-to: 6.10 6.9 Change-Id: I650e3328ef3830d06206acafc3305566d3a10d86 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add API for extension managementMartin Negyokru2025-05-291-0/+10
| | | | | | | | | | | | | | | Introduce QWebEngineExtensionManager and QWebEngineExtensionInfo. The manager has methods to load and install Chrome extensions from the filesystem. QWebEngineExtensionInfo provides information about a loaded extension. The current state of our js extension API support is very limited meaning most of the extensions downloaded from Chrome extension store won't work. Adding support for these APIs will be done in followup patches. Fixes: QTBUG-118452 Task-number: QTBUG-61676 Change-Id: I017ad5e8d2ba963afbd2f31ac36fee9451a951bd Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add API for providing additional CA certificatesKai Uwe Broulik2025-05-271-1/+8
| | | | | | | | | | This allows to provide additional certificates that are considered when verifying a certificate. This is done by the cert verifier downstream of the platform-specific cert store. Fixes: QTBUG-50586 Change-Id: Ie90547f1013f22f994aaff536fadf906a44a88ef Reviewed-by: Moss Heim <moss.heim@qt.io>
* Client Hints: Improve version listsSzabolcs David2025-05-221-8/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are several issues affecting Sec-CH-UA and -Full-Version-List, because the general algorithm which extends and shuffles these lists was not used in WebEngine. At the current version of Chromium we can't use the corresponding user agent utils functions, because they only allow one extra brand/version pair besides the two generated (Chromium and Not-A-Brand) ones. This change implements a simplified method to extend and shuffle the version lists to follow the behavior of Chromium and support more than three elements. QTBUG-133799: The order of brands and versions are still not customizable by the API user, but it is permutated in each major version of Chromium to comply with the standards. To allow customization of the order seems to be impossible without changing our public API. QTBUG-133708: The missing values of Sec-CH-UA are generated from the full version list, not customizable individually. This way it keeps the same values and the same algorithmically generated order as the full version list. Task-number: QTBUG-133711 Task-number: QTBUG-133708 Task-number: QTBUG-133777 Task-number: QTBUG-133799 Change-Id: I96f214ce54190666a34779130a04b56f600abef7 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu> Reviewed-by: Moss Heim <moss.heim@qt.io>
* Add support for Sec-CH-UA-Form-FactorsAnu Aliyas2025-03-111-0/+15
| | | | | | | | | | Added new APIs in QWebEngineClientHints to add support for Sec-CH-UA-Form-Factors. Fixes: QTBUG-133709 Change-Id: I525bdebcdd490413457e93e6ebef6c6be125c9b6 Reviewed-by: Szabolcs David <davidsz@inf.u-szeged.hu> Reviewed-by: Moss Heim <moss.heim@qt.io>
* Replace QStringLiteral with shorter u""_s notationPeter Varga2025-02-211-2/+2
| | | | | | Pick-to: 6.8 6.9 Change-Id: I6d45505c808a48a1ea52ddbd39e74ada4c29136d Reviewed-by: Marc Mutz <marc.mutz@qt.io>
* Optimize removing quality values from Accept-Language stringPeter Varga2025-02-211-5/+5
| | | | | | | | | | Also add auto test for QWebEngineProfile::setHttpAcceptLanguage() to validate if argument with quality values is parsed properly. Pick-to: 6.8 6.9 Change-Id: Ide3acfe93bfe2d4c6afd76bd7239f471942ea467 Reviewed-by: Marc Mutz <marc.mutz@qt.io> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Make QString and QByteArray strings constants if not modifiedPeter Varga2025-02-211-3/+3
| | | | | | Pick-to: 6.8 6.9 Change-Id: If6c704cf5dada72d2c5c069fcbbcfea16af845ac Reviewed-by: Marc Mutz <marc.mutz@qt.io>
* Unify and modernize Latin1 string literalsPeter Varga2025-02-081-4/+7
| | | | | | | | | | | - Fix some deprecated string literal compiler warnings - Replace deprecated QLatin1String usages - Use QLatin1StringView where QString conversion is not needed - Replace QLatin1StringView usages with shorter _L1 suffix Pick-to: 6.8 6.9 Change-Id: I8adb6dcd06ac5dfc248d39455c14a26957876512 Reviewed-by: Marc Mutz <marc.mutz@qt.io>
* Ensure unique data path for the profileAnu Aliyas2024-12-061-0/+5
| | | | | | | | | | | Added data path verification to restrict profile creation. This change ensures that no two profiles can use the same data path. Any request to create a profile with the duplicate data path will now return nullptr. Change-Id: Ifb25861756775fb484b02a23c802bffb791c88bb Reviewed-by: Michael Brüning <michael.bruning@qt.io> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Add QWebEngineProfileBuilder classAnu Aliyas2024-12-041-6/+16
| | | | | | | | | | | | | | | | | | | | This is a wrapper designed to handle profile construction. The QWebEngineProfile class allows the modification of profile storage properties, which is against chromium profile design. Changing storage properties requires the recreation of storage and network context leading to hacks, which in turn leads to bugs. The QWebEngineProfileBuilder aims to prevent modification of storage properties and set them at the profile creation time. The current change introduces new APIs without deprecating the storage setters in the QWebEngineProfile class. The final goal is to deprecate the storage setters and constructor from QWebEngineProfile and use the QWebEngineProfileBuilder to create profiles. Task-number: QTBUG-66068 Change-Id: I3c2562c9e1445708f0dbdeae5783a8c7d38313af Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* Make download API asynchronousSzabolcs David2024-10-241-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | Modify the already existing downloadRequest() API. Now the requests not necessarily have to be answered in a directly connected signal handler and the API users can postpone their user's decision. The only exceptions are automatically accepted save page requests. There is no better place to call their callback than directly after the signal emission. Adapt auto tests to the new lifecycle of download items. Modify the quicknanobrowser example to use a simple async method to wait for the user's decision. Keep simplebrowser to use its old synchronous method to illustrate that it's still possible. Correct documentation at some places. [ChangeLog] QWebEngineProfile::downloadRequested() is not limited to synchronous usage anymore. QWebEngineDownloadRequest can be accepted or rejected later without blocking the browsing session. Fixes: QTBUG-118584 Change-Id: Ic1be6508126574dc77aa686f85bf35feafdb080d Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Remove redundant codeAllan Sandfeld Jensen2024-10-111-8/+0
| | | | | | | | | We do not pass on id to Chromium, so it is pointless to generate. Extensions are initialized from profile_qt.cpp so no reason to do it in profile_adapter.cpp Change-Id: I5e38d71a163e4cd39943bb1818c1273d6591724d Reviewed-by: Szabolcs David <davidsz@inf.u-szeged.hu>
* Fix history service reinitalizationMartin Negyokru2024-10-071-0/+8
| | | | | | | | | | | | | | | setStorageName and setPersistenStoragePath did not update the storage path of the history service if the service was already initialized. It is not supported to change the service's path manually, so reset the service instead. The favicon service also needs to be reseted for similar reasons. This change fixes the flaky test_iconDatabaseMultiView test. Change-Id: I53fb49832615ea334df30e16167bd32fdaa59038 Reviewed-by: Szabolcs David <davidsz@inf.u-szeged.hu> Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Adaptations for Chromium 126Allan Sandfeld Jensen2024-09-261-5/+5
| | | | | | Change-Id: If920f024c9f8fe18a9f22fa97b8fb5564dfa3b61 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu> Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix crash on Windows when storing blobs on diskKaloyan Chehlarski2024-08-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | As a security feature, files that may get accessed by multiple threads on Windows get marked with a deny execute ACE when written to disk, which prevents them from being opened for execution later on. Unfortunately, the directories allowed to have files marked like this are limited, and need explicit opt-in. This triggers a debug crash whenever a blob is to be written to disk, since the target directory is not in that list. This change ensures that profile storage directories (including custom ones set by the user) get added to that list. We do so by keeping our own static list of all storage paths needed by non-OTR profiles, and making sure that said list is passed to Chromium whenever a new storage path is to be used. However, the code in this commit only ensures that the last registered profile path will work correctly, since Chromium does not expect an embedder to allow multiple non-OTR profiles alive at the same time, each with its own arbitrary storage path. To make this use case work, the underlying code in the path service is also changed in a separate Chromium change. Pick-to: 6.7 6.8 Change-Id: Ic0f12f8e444fc0c6325cc2f1ee06a0b73634e398 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Permission manager: separate tracking of transient permissionsKaloyan Chehlarski2024-08-241-7/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Following the rewrite of the permissions API, transient (a.k.a non-persistent) permissions still passed through the persistent store sometimes, but were filtered out when using user-facing APIs. Unfortunately, thisstill presented some edge cases in the AskEveryTime permission policy mode. This change modifies the PermissionManagerQt class to store a second set of permissions, and associate them with a RenderFrameHost the way the Chromium API is designed to do anyway. This way, a permission will be kept around for the lifetime of a web page, and calling JavaScript APIs that trigger checks for permission state will work properly (e.g. navigator.mediaDevices.enumerateDevices). The new store is regularly cleaned up to make sure expired permissions are purged before they impact performance. As a side effect, this change also introduces pre-granting of non-persistent permissions, which was the biggest omission in the permissions rewrite. In those cases, the permissions will be temporarily stored inside the persistent store, and moved to the transient one the next time they're queried (and can thus be associated with a RenderFrameHost). This also fixes some extremely broken test cases that relied on invalid web API. Fixes: QTBUG-127951 Pick-to: 6.8 Change-Id: Ic084af7673ea0b255d98d94382e77323bb5e7ab0 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* QWebEnginePermission: Post-API reviewKaloyan Chehlarski2024-07-031-13/+14
| | | | | | | | | | | | | | | This commit contains fixes for the issues found during the API review of the new permissions API. In particular: - All new enums are now scoped - Replaced isTransient with its opposite, isPersistent - Renamed Feature to PermissionType - Made origin() return a non-const QUrl - Renamed PersistentPermissionsPolicy members to be more concise - Fixed a couple of bugs in the implementation - Updated documentation Change-Id: Idf84e1c9ba3ae803ef4686e1caa7f3e6c198c87d Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Adaptations for Chromium 122Michal Klocek2024-06-071-10/+9
| | | | | | | | | | | | | | | | | Includes following patches: * 340b36c Bind SpellCheckHost to a RenderFrameHost * f154285 Fix chrome://ukm webui after 122 update * 3e67d86 Adapt datalist test to new Chromium behavior after 122 adaptations * 76b532e Fix test failures in tst_accessibility * 8a9ecf5 Adapt IME test to new Chromium behavior after 122 adaptations * d65cd90 Fix to resolve the DCHECK failure during download operation * e956d1d Ensure DelegatedFrameHost's frame sink ID is registered Done-With: Anu Aliyas, Kaloyan Chehlarski, Martin Negyokru, Peter Varga Pick-to: 6.8 Change-Id: Ic5e8c0457c1633af18a8e11785041ab423e9362e Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Adaptations for Chromium 120Allan Sandfeld Jensen2024-06-071-1/+0
| | | | | | Pick-to: 6.8 Change-Id: I487d2c6cf56fdda5fb95e6b2715e7dbc42527c2d Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Implement API for listing existing permissions in a profileKaloyan Chehlarski2024-06-031-0/+11
| | | | | | | | | | | QWebEngineProfile and QQuickWebEngineProfile now have methods for either getting one specific permission object, or for getting a list of all the permissions currently stored. The methods for listing also have overloads for filtering based on origin or Feature type. Pick-to: 6.8 Change-Id: I07241bcb3ff171fa8b82547c2b5f094071bebe44 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add QWebEnginePermission and rewrite permissions APIKaloyan Chehlarski2024-06-031-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With the addition of permission persistence, it's now important for us to have an API for querying previously granted/denied permissions, so that they can be revoked at a later point. This change does the bulk of the work to get us there, by introducing a new type representing a single permission for a given URL/Feature pair. This type holds no information about the permission's state; it is simply an accessor object which allows its user to query the current status of the permission, grant/deny it, or reset it back to its initial state (so, delete it from storage). This provides application developers an easy way to store/modify lists of permissions without having to define their own custom types. A subsequent change will expand the API to provide a list of all permissions for a given profile. The current API (in QWebEnginePage and QQuickWebEngineView) has been marked as deprecated, but has not been disabled to ensure a smooth transition for developers. [ChangeLog][QtWebEngineCore][QWebEnginePage] Deprecated old permissions API [ChangeLog][QtWebEngineQuick][WebEngineView] Deprecated old permissions API [ChangeLog][QtWebEngineCore] Added new API for querying and modifying website permissions. [ChangeLog][QtWebEngineQuick] Added new API for querying and modifying website permissions. Pick-to: 6.8 Change-Id: I8661cdc26bbd6dcde6403d29cc083bcea1a49ccc Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Implement optional website permission persistenceKaloyan Chehlarski2024-06-011-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | This change introduces a new API allowing application developers to choose whether they want to retain the granted/denied status of permissions between different pages or browsing sessions. The previous behavior of asking for permission every time is still optionally available, but the default behavior is to persist permissions inbetween sessions (except for off-the-record profiles, where the permissions get destroyed alongside the profile). Storage is handled via a PrefService, which writes to a permissions.json file stored inside the profile folder. This is different to Chromium's implementation, which is massively overengineered and would require enabling a ton of code we will never need to use. [ChangeLog][QtWebEngineCore][QWebEngineProfile] Added new API to control permission persistence. [ChangeLog][QtWebEngineQuick] Added new API to control permission persistence. Fixes: QTBUG-55108 Change-Id: Ib3057feda3bfbbf2a17a86356feca35a67180806 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add API to override User Agent Client HintsSzabolcs David2023-12-141-2/+112
| | | | | | | | | | | Implement QWebEngineClientHints class to provide API for each user agent client hints. Task-number: QTBUG-112826 Task-number: QTBUG-112825 Change-Id: I3091d60fb363bbafc16c8e48195c1fd82e8a81bb Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
* Allow cancelling automatically accepted download requestsSzabolcs David2023-10-171-2/+2
| | | | | | | | | | | | | Calling QWebEngineDownloadRequest::cancel() had no effect if the download request was accepted by default. These downloads had no corresponding internal DownloadItem yet, but we tried to cancel them using the DownloadManager. The safest option is to always check if the DownloadItem exists in Chromium. Pick-to: 6.6 Task-number: QTBUG-117624 Change-Id: I8f92d45e00e088aea7d22d5b7271b5b09adf6cbb Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix corrupted load/fetch state on start up in case of NoCacheMichal Klocek2023-10-121-2/+0
| | | | | | | | | | | | | | | | | | | | The NoCache option on profile schedules clearHttpCache task. However, this task will run later and BrowsingDataRemover will break current network context mojo pipes. Network context will be recreated eventually but all the load/request states are gone. Do not delete explicitly cache on NoCache setting, which was undocumented 'feature' anyway. Let the user take care of that. Note doing reset network context on startup is fine as it is not delayed. [ChangeLog][WebEngineCore][WebEngineProfile] Switching profile to NoCache do not longer implicitly removes cache from old data store. Pick-to: 6.6 6.5 Task-number: QTBUG-116478 Change-Id: Ibd108d4ce7392349304df9f606738dc14dba36a0 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Remove QWebEngineUrlResponseInterceptor APIMichael Brüning2023-08-241-10/+0
| | | | | | | | | | | | | | | | | It has been found to not have any real effect, therefore, we remove it again to not release a non-functional API and create false expectations in users. This reverts commits 3f5de5fab74e6c152cdf5d04f3d893feaa31790b ab21f39c6a54be331dd8a155d3374bfe790e0274 (parts) 082eef1916a86d6d5e0c751d271c7c8a1a5e457d 5e257fb57a211f95556ec387fe6f262a60cbb6fe Pick-to: 6.6 Task-number: QTBUG-61071 Change-Id: Ifb33e32128e77dfffed863a1a7501ba21796692d Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Adaptations for Chromium 112Allan Sandfeld Jensen2023-07-061-3/+3
| | | | | | Pick-to: 6.6 Change-Id: I1bb84b20a080d7f615bf0795ac2d97739e99ac1d Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* QWebEngineUrlResponseInterceptor: Implement new URL response interceptorYigit Akcay2023-03-101-0/+10
| | | | | | | | | | | | | | | | | | | | | This patch adds the QWebEngineUrlResponseInterceptor abstract class, which, when implemented, allows a user to intercept response headers and modify them in any way they like. A response interceptor can be set via QWebEngineProfile::setUrlResponseInterceptor(), QQuickWebEngineProfile::setUrlResponseInterceptor() or QWebEnginePage::setUrlResponseInterceptor(). Also, the QWebEngineUrlResponseInfo class is implemented, which contains the request and response data to be used with the response interceptor. If a response interceptor is set in the profile and page, the one in the profile takes precedence. Fixes: QTBUG-61071 Change-Id: I484d14373ff597b1d531541c066f0102bae28c72 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* Remove setPushServiceEndpoint from APIMichal Klocek2022-12-221-4/+5
| | | | | | | | | | Use setPushServiceEnabled instead. Update also getter and documentation. Task-number: QTBUG-107442 Pick-to: 6.5 Change-Id: I299ce88b06edef0f1a0088fb10f4a142056039be Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* Enable Push MessagingSzabolcs David2022-09-121-0/+12
| | | | | | | | | | | | | | | | | | Use Chrome's implementation of PushMessagingService. This feature relies on notification permissions, so it is not different from Web Notification from end-users perspective. We don't persist push subscriptions, because it seems these have to be consistent with persisting notification permissions. Make address of push service configurable by a profile setting. It is empty by default - which means the feature is disabled until the user sets the address of a push service. Task-number: QTBUG-98904 Task-number: QTBUG-53457 Change-Id: If44f459fecf2da482c28fee5562f62fe40de103e Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Use SPDX license identifiersLucie Gérard2022-06-221-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: I869ffda1080e283f231eb0dc4477b260f2054d99 Reviewed-by: Jörg Bornemann <joerg.bornemann@qt.io>
* Protect against default profile being deleted before its pagesAllan Sandfeld Jensen2022-06-131-3/+8
| | | | | | | | | Can really only happen in QML on exit. Pick-to: 6.3 6.4 Task-number: QTBUG-99445 Change-Id: I1a04d57b6c4c40ae264b5519d2e41c57bca79a61 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Fix build on Mac M1Szabolcs David2022-04-061-0/+1
| | | | | Change-Id: I27bc0a6dcd91d3c7059479ea464b24c47bb76420 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Adaptations for Chrome 98Allan Sandfeld Jensen2022-03-291-1/+5
| | | | | Change-Id: I607604f85a111a69da77ca949dddf3399b9721b3 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Adaptations for Chrome 96Allan Sandfeld Jensen2022-03-291-2/+23
| | | | | Change-Id: I40039658762b8788a0be57bd186efab71f3e4448 Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Clean up includes in profile_adapterMartin Negyokru2022-03-241-7/+3
| | | | | Change-Id: If345d774651b801362da67ff9d3f80867662b29d Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Adaptations for Chromium 94Allan Sandfeld Jensen2021-12-021-0/+1
| | | | | Change-Id: I9fb8998a3a7762b0aea70993ca231f0bbf4f7761 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Adaptations for Chromium 92Allan Sandfeld Jensen2021-12-021-14/+14
| | | | | Change-Id: I1849c130ca75615802744275f6e4212a755c39b4 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* Remove deprecated useforglobalcertificateverificationPeter Varga2021-07-061-35/+0
| | | | | | | | | | | | It enabled an unrecommended OCSP path on Linux [ChangeLog] (Q)WebEngineSettings::useForGlobalCertificateVerification has been removed. Pick-to: 6.2 Task-number: QTBUG-91467 Change-Id: I9f5d1ad5e4fcb59abd31e6a133ded7bf8319c811 Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
* Cancel favicon requests explicitlyAllan Sandfeld Jensen2021-07-021-0/+1
| | | | | | | | Better to do it before we invalidate the profile. Pick-to: 6.2 Change-Id: I2448bc522a973d26cb51aebe2f413bf30ca3edef Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* Remove QRC->file special caseAllan Sandfeld Jensen2021-07-011-11/+0
| | | | | | | | It was marked as to be removed for Qt6 Pick-to: 6.2 Change-Id: I059c450aa6e5cad6d48ecdd2667abff21217d7e0 Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
* Add API for favicon databasePeter Varga2021-06-181-0/+99
| | | | | | | | | | | | [ChangeLog][QtWebEngineCore][QWebEngineProfile] Add new API to access icon database asynchronously. [ChangeLog][QtWebEngineQuick] image:/favicon/ URLs now can be used to access icon database. Pick-to: 6.2 Task-number: QTBUG-51184 Change-Id: I6096ad9a4210670ed59458c4fa099a02595e8a1e Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Replace FaviconManager with Chromium's Favicon ComponentPeter Varga2021-06-041-0/+33
| | | | | | Task-number: QTBUG-51184 Change-Id: Ie050cb23f2c86841a66ec384bfbcdf0713cffa7c Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Merge remote-tracking branch 'origin/5.15' into devAllan Sandfeld Jensen2021-05-121-14/+17
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: examples/webenginewidgets/printme/printhandler.cpp src/3rdparty src/core/api/qwebenginepage_p.h src/core/content_browser_client_qt.h src/core/web_contents_adapter_client.h src/core/web_contents_delegate_qt.cpp src/core/web_contents_delegate_qt.h src/webenginequick/api/qquickwebengineview_p_p.h tests/auto/quick/qmltests/data/tst_download.qml tests/auto/quick/qmltests/data/tst_viewSoure.qml tests/auto/widgets/loadsignals/tst_loadsignals.cpp tests/auto/widgets/qwebengineview/tst_qwebengineview.cpp Change-Id: I9c1819ec15e13d4f8e244defe860e26274b5d4be
| * Allow leaving OCSP offAllan Sandfeld Jensen2021-05-031-14/+17
| | | | | | | | | | | | | | | | | | | | This form of OCSP is not good, so try to at least allow it to be disabled, until we remove it. Fixes: QTBUG-91467 Change-Id: Ied9e8c4960e6ea1503dea39ebbced2ad1af08d5d Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
* | Adaptations for Chromium 88Allan Sandfeld Jensen2021-04-151-1/+1
| | | | | | | | | | Change-Id: Ie66e95dbb9fbcafe961bb98d5c277f8c32d66b96 Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-15 17:52:42 +0000