Add Accessibility Object Model to chrome://flags
This is important for testing on Chrome OS and Android where it's not
always possible to run Chrome with a command-line switch.
Bug: 746523
Change-Id: I8326cdaa44b6013dd0b6a9d1c1f7ca1022cb208e
Reviewed-on: https://chromium-review.googlesource.com/1072505
Reviewed-by: John Abd-El-Malek <[email protected]>
Commit-Queue: Dominic Mazzoni <[email protected]>
Cr-Commit-Position: refs/heads/master@{#561778}diff --git a/chrome/browser/about_flags.cc b/chrome/browser/about_flags.cc
index 15790f9..cc5c680 100644
--- a/chrome/browser/about_flags.cc
+++ b/chrome/browser/about_flags.cc
@@ -3889,6 +3889,11 @@
FEATURE_VALUE_TYPE(app_list::features::kEnableAppShortcutSearch)},
#endif // OS_CHROMEOS
+ {"enable-accessibility-object-model",
+ flag_descriptions::kEnableAccessibilityObjectModelName,
+ flag_descriptions::kEnableAccessibilityObjectModelDescription, kOsAll,
+ SINGLE_VALUE_TYPE(switches::kEnableAccessibilityObjectModel)},
+
// NOTE: Adding a new flag requires adding a corresponding entry to enum
// "LoginCustomFlags" in tools/metrics/histograms/enums.xml. See "Flag
// Histograms" in tools/metrics/histograms/README.md (run the
