mirror of
https://bitbucket.org/chromiumembedded/cef
synced 2025-06-05 21:39:12 +02:00
alloy: Remove optimization/prediction service usage (see issue #3352)
This service is required by the "PermissionOnDeviceNotificationPredictions" feature which is enabled by default in https://crbug.com/1350956. It uses a Google backend service as described at https://go.dev/solutions/google/chrome. This change removes the usage of PredictionBasedPermissionUiSelector, which triggered this dependency, along with related startup complexity that was added to support the optimization/prediction service in the M106 update.
This commit is contained in:
@@ -29,8 +29,7 @@ class CefRequestContextImpl : public CefRequestContext {
|
||||
|
||||
// Creates the singleton global RequestContext. Called from
|
||||
// AlloyBrowserMainParts::PreMainMessageLoopRun and
|
||||
// ChromeBrowserMainExtraPartsCef::PostProfileInit. Must be followed by a call
|
||||
// to InitializeGlobalContext on the UI thread.
|
||||
// ChromeBrowserMainExtraPartsCef::PostProfileInit.
|
||||
static CefRefPtr<CefRequestContextImpl> CreateGlobalRequestContext(
|
||||
const CefRequestContextSettings& settings);
|
||||
|
||||
@@ -39,8 +38,6 @@ class CefRequestContextImpl : public CefRequestContext {
|
||||
static CefRefPtr<CefRequestContextImpl> GetOrCreateForRequestContext(
|
||||
CefRefPtr<CefRequestContext> request_context);
|
||||
|
||||
void InitializeGlobalContext();
|
||||
|
||||
// Verify that the browser context can be directly accessed (e.g. on the UI
|
||||
// thread and initialized).
|
||||
bool VerifyBrowserContext() const;
|
||||
|
Reference in New Issue
Block a user