From dd2acb8a0a5ccbbf34664987fdcf4b3a418c54f9 Mon Sep 17 00:00:00 2001 From: Allan Sandfeld Jensen Date: Thu, 15 Feb 2018 17:58:31 +0100 Subject: Tie worker rights to cookie policy like Chromium does Instead of always allowing all workers, disallow when similar cookies would have been disallowed. This is following the same logic as Chromium is using. Change-Id: I6b9d6c63b894287f64171b138fe03ec080af5115 Reviewed-by: Leena Miettinen Reviewed-by: Peter Varga --- src/core/api/qwebenginecookiestore.cpp | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'src/core/api/qwebenginecookiestore.cpp') diff --git a/src/core/api/qwebenginecookiestore.cpp b/src/core/api/qwebenginecookiestore.cpp index adf0cc49e..76e79c570 100644 --- a/src/core/api/qwebenginecookiestore.cpp +++ b/src/core/api/qwebenginecookiestore.cpp @@ -353,6 +353,10 @@ void QWebEngineCookieStore::deleteAllCookies() The callback should not be used to execute heavy tasks since it is running on the IO thread and therefore blocks the Chromium networking. + \note The cookie filter also controls other features with tracking capabilities similar to + those of cookies; including IndexedDB, DOM storage, filesystem API, service workers, + and AppCache. + \sa deleteAllCookies(), loadAllCookies() */ void QWebEngineCookieStore::setCookieFilter(const std::function &filterCallback) -- cgit v1.2.3