summaryrefslogtreecommitdiffstats
path: root/examples/webenginewidgets/push-notifications
Commit message (Collapse)AuthorAgeFilesLines
* Add QWebEngineProfileBuilder classAnu Aliyas2024-12-041-1/+3
| | | | | | | | | | | | | | | | | | | | 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>
* QWebEnginePermission: Post-API reviewKaloyan Chehlarski2024-07-031-1/+1
| | | | | | | | | | | | | | | 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>
* Fix QWEPermission related warningsMartin Negyokru2024-06-241-1/+1
| | | | | | | | | Fix compiler warnings that are related to QWebEnginePermission. Pick-to: 6.8 Change-Id: Icac1352e4934f73a205b85896b6f83171b759dd3 Reviewed-by: Kaloyan Chehlarski <kaloyan.chehlarski@qt.io> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add QWebEnginePermission and rewrite permissions APIKaloyan Chehlarski2024-06-031-5/+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>
* Correct license for examples filesLucie Gérard2024-04-091-1/+1
| | | | | | | | | | | | | Example takes precedence over build system file type. According to QUIP-18 [1], all examples file should be LicenseRef-Qt-Commercial OR BSD-3-Clause [1]: https://contribute.qt-project.org/quips/18 Pick-to: 6.7 Task-number: QTBUG-121787 Change-Id: I558c6f409a480835d335101577ae633194b0559d Reviewed-by: Kai Köhne <kai.koehne@qt.io>
* Doc: Update example category namesKai Köhne2023-08-101-1/+1
| | | | | | | | | | | | | | | | WebEngine examples are generally added to the new 'Web Technologies' category - only Nano Browser remains also in the 'Application Examples' category. The 2 Qt PDF examples are placed in the 'Graphics & Multimedia' category. This is not ideal, but from the existing categories the arguably best matching one. Pick-to: 6.5 6.6 Task-number: QTBUG-115174 Change-Id: I3824272f62a4940f91041c8694fd2a06929863ed Reviewed-by: Venugopal Shivashankar <Venugopal.Shivashankar@qt.io> Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
* Set example category on Widgets examplesAllan Sandfeld Jensen2023-06-201-0/+1
| | | | | | | Pick-to: 6.6 6.5 6.5.2 Change-Id: I795da5e37bd084e5c101aaed14fda5a9b3be4b92 Reviewed-by: Kimmo Leppälä <kimmo.leppala@qt.io> Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
* Update push example after setPushServiceEndpoint changeMichal Klocek2022-12-227-7/+204
| | | | | | | | | | | | We have now extra call to enable push messaging, therefore drop usage of simple browser in example and use the same code as in Notification Example but add new settings and fix profile to be not off-the-record. Task-number: QTBUG-107442 Pick-to: 6.5 Change-Id: I3069c4cf2b6a6ce864c1e4c578ab03adb67984e4 Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
* Fix qdoc warningsMichal Klocek2022-12-1612-0/+1246
As JavaScript parsing issue got fixed , the limit was not changed, meaning there where 4 "unused" warnings possibilities. In the meantime another change e6a13d97898f3f4b19f61006d0716ca9e1b9f037 was merged which had 3 qdoc issues, which got therefore unnoticed. Fix those issues. Do not use underscore in example name and rename push_notification to push-notifications (like qtbase network-chat). Pick-to: 6.5 Change-Id: I2635424e24d3b9a0a02c2e6fe8ac383eec95c112 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-17 08:35:29 +0000