Temporarily disable two-finger spoken feedback toggle.

chrome/browser/chromeos/accessibility/accessibility_manager.cc

Index: chrome/browser/chromeos/accessibility/accessibility_manager.cc
diff --git a/chrome/browser/chromeos/accessibility/accessibility_manager.cc b/chrome/browser/chromeos/accessibility/accessibility_manager.cc
index 6c43cf7428acb4506ed12489624441be649c6aeb..f6268fe2cb0c0841dea6a1396317db238b227d56 100644
--- a/chrome/browser/chromeos/accessibility/accessibility_manager.cc
+++ b/chrome/browser/chromeos/accessibility/accessibility_manager.cc
@@ -562,6 +562,11 @@ bool AccessibilityManager::PlayEarcon(int sound_key, PlaySoundOption option) {
 }
 
 bool AccessibilityManager::ShouldToggleSpokenFeedbackViaTouch() {
+#if 1
+  // Temporarily disabling this feature until UI feedback is fixed.
+  // http://crbug.com/662501
+  return false;
+#else

[David Tseng, 2017/01/31 20:55:31]

Why not just remove this block?

[dmazzoni, 2017/01/31 21:02:30]

The CFM team is going to follow up with a patch to change
the UI and then re-enable this. I didn't want to remove this
code and have the possibility of accidentally losing the
logic when it's re-enabled. That's why I though this would
be more clear - otherwise you'd have to know to revert this
change when re-enabling it and not just return true.

But if you still think it's better to delete the code and
maybe just leave a comment, let me know. Either way.

   policy::BrowserPolicyConnectorChromeOS* connector =
       g_browser_process->platform_part()->browser_policy_connector_chromeos();
   if (!connector)
@@ -582,6 +587,7 @@ bool AccessibilityManager::ShouldToggleSpokenFeedbackViaTouch() {
   KioskAppManager::App app;
   CHECK(manager->GetApp(manager->GetAutoLaunchApp(), &app));
   return app.was_auto_launched_with_zero_delay;
+#endif
 }
 
 bool AccessibilityManager::PlaySpokenFeedbackToggleCountdown(int tick_count) {