Make sure all users in the Control group get to see the widget.
The widget enabled state is retained by the package manager.
All users who were in the control group will not receive the
widget until that state is corrected, otherwise the offering
will persist.
The change partially reverts the mechanism that was used to
conditionally disable Widget for users in Control group, and
uses it to unconditionally enable it for everyone.
The restored code taken from http://shortn/_NL8d3BYmTI.
Bug: 1309116
Change-Id: I3c55fec71c2d21711f605454f0793135f9c3fe53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3543325
Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Tomasz Wiszkowski <ender@google.com>
Auto-Submit: Tomasz Wiszkowski <ender@google.com>
Cr-Commit-Position: refs/heads/main@{#983976}
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/quickactionsearchwidget/QuickActionSearchWidgetProvider.java b/chrome/android/java/src/org/chromium/chrome/browser/quickactionsearchwidget/QuickActionSearchWidgetProvider.java
index c1d6193..8f5bcc0 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/quickactionsearchwidget/QuickActionSearchWidgetProvider.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/quickactionsearchwidget/QuickActionSearchWidgetProvider.java
@@ -21,6 +21,8 @@
import org.chromium.base.ContextUtils;
import org.chromium.base.IntentUtils;
import org.chromium.base.ThreadUtils;
+import org.chromium.base.task.PostTask;
+import org.chromium.base.task.TaskTraits;
import org.chromium.chrome.browser.IntentHandler;
import org.chromium.chrome.browser.browserservices.intents.WebappConstants;
import org.chromium.chrome.browser.document.ChromeLauncherActivity;
@@ -249,6 +251,12 @@
private static void setWidgetComponentEnabled(
@NonNull Class<? extends QuickActionSearchWidgetProvider> component,
boolean shouldEnableWidgetComponent) {
+ PostTask.postTask(TaskTraits.BEST_EFFORT, () -> {
+ // Make the Widget available to all Chrome users who participated in an experiment in
+ // the past. This can trigger disk access. Unfortunately, we need to keep it for a
+ // little bit longer -- see: https://crbug.com/1309116
+ setWidgetEnabled(true, true);
+ });
// The initialization must be performed on a background thread because the following logic
// can trigger disk access. The PostTask in ProcessInitializationHandler can be removed once
// the experimentation phase is over.
