summaryrefslogtreecommitdiff
path: root/src/core/api/qwebengineprofile.h
diff options
context:
space:
mode:
authorSzabolcs David <davidsz@inf.u-szeged.hu>2022-03-10 18:11:49 +0100
committerSzabolcs David <davidsz@inf.u-szeged.hu>2022-09-12 18:01:24 +0200
commit0ca4eba9612fbcba988ca06c47f5738d4cb71fbd (patch)
tree2a7b609c44f7c5c9a5fd993e154d3b16f32e031b /src/core/api/qwebengineprofile.h
parent74163a6511278fa8273ca931ffdf9b9b3a8daae6 (diff)
downloadqtwebengine-0ca4eba9612fbcba988ca06c47f5738d4cb71fbd.tar.gz
Enable Push Messaging
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>
Diffstat (limited to 'src/core/api/qwebengineprofile.h')
-rw-r--r--src/core/api/qwebengineprofile.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/core/api/qwebengineprofile.h b/src/core/api/qwebengineprofile.h
index c29202973..cd711727b 100644
--- a/src/core/api/qwebengineprofile.h
+++ b/src/core/api/qwebengineprofile.h
@@ -98,6 +98,9 @@ public:
QString downloadPath() const;
void setDownloadPath(const QString &path);
+ QUrl pushServiceEndpoint() const;
+ void setPushServiceEndpoint(const QUrl &endpoint);
+
void setNotificationPresenter(std::function<void(std::unique_ptr<QWebEngineNotification>)> notificationPresenter);
QWebEngineClientCertificateStore *clientCertificateStore();