summaryrefslogtreecommitdiffstats
path: root/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java
diff options
context:
space:
mode:
authordfalcantara <dfalcantara@chromium.org>2016-03-25 16:37:20 -0700
committerCommit bot <commit-bot@chromium.org>2016-03-25 23:40:01 +0000
commitde49c2d22f6c873aac94696ef004ecf8d8dd6b52 (patch)
treea8e840389d80424c9c3bc715a9cda864efa72dd7 /chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java
parent0e22e7e8fe94d4f4deadcb2d6460e6a1ca38cd35 (diff)
downloadchromium_src-de49c2d22f6c873aac94696ef004ecf8d8dd6b52.zip
chromium_src-de49c2d22f6c873aac94696ef004ecf8d8dd6b52.tar.gz
chromium_src-de49c2d22f6c873aac94696ef004ecf8d8dd6b52.tar.bz2
Add pathway to auto-migrate users when Chrome launches
* For now, a command line flag is required to trigger this pathway: --enable-forced-migration * UpgradeActivity kicks off the DocumentModeAssassin and waits for it to finish. This Activity can only be launched via other ChromeActivities, and can be passed an Intent to refire when the migration finishes. * A MAIN Intent or Intent to start a new DocumentActivity that goes through ChromeLauncherActivity will force users through UgpradeActivity, instead. This causes document mode to be flipped off, and anything going down the ChromeLauncherActivity pathway again should no longer trigger migration. This pathway catches new tabs created via VIEW Intents, MAIN Intents, CCT Intents, and (sometimes) WebappActivity Intents. * AsyncInitializationActivity watches for the need for the migration pathway to be triggered when a ChromeActivity subclass starts up. This pathway catches Intents that skip ChromeLauncherActivity, which includes ChromeTabbedActivity, DocumentActivity, CustomTabActivity, and WebappActivity. These can be launched directly by selecting them from Android Recents, or by firing Intents to bring them back specifically. * The look of this Activity is a stand-in for when we get redlines. The animation is also kind of janky, but I'm aiming for functionality at this point. * TabDelegate is no longer allowed to create new DocumentActivities, instead deferring down the ChromeLauncherActivity pathway. This catches cases with push notifications triggering a tab to be created when they're clicked. * The preference to enable document mode is hidden once the user has migrated. BUG=582539 Review URL: https://codereview.chromium.org/1817083003 Cr-Commit-Position: refs/heads/master@{#383406}
Diffstat (limited to 'chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java')
-rw-r--r--chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java5
1 files changed, 5 insertions, 0 deletions
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java b/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java
index 534fdef..07c8b0f 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/ChromeSwitches.java
@@ -231,6 +231,11 @@ public abstract class ChromeSwitches {
"disable-web-notification-custom-layouts";
/**
+ * Forces a user down the document to tabbed mode migration pathway.
+ */
+ public static final String ENABLE_FORCED_MIGRATION = "enable-forced-migration";
+
+ /**
* Determines which of the Herb prototypes is being tested.
* See about:flags for descriptions.
*/