Deprecating high-conflict accelerators

ui/views/focus/focus_manager.h

Index: ui/views/focus/focus_manager.h
diff --git a/ui/views/focus/focus_manager.h b/ui/views/focus/focus_manager.h
index aa8f66a1d481cbf45aa29cec83d7396235f86c2c..090cce57ce81bbf085f2cfaf87e6df47c018ad72 100644
--- a/ui/views/focus/focus_manager.h
+++ b/ui/views/focus/focus_manager.h
@@ -259,6 +259,10 @@ class VIEWS_EXPORT FocusManager {
   // Returns true if an accelerator was activated.
   bool ProcessAccelerator(const ui::Accelerator& accelerator);
 
+  // Returns true if the given |accelerator| has been deprecated and hence can
+  // be consumed by web contents if needed.
+  bool IsAcceleratorDeprecated(const ui::Accelerator& accelerator) const;

[sky, 2015/06/18 15:25:18]

Feels wrong to put this logic in FocusManager when it doesn't care about
deprecated accelerators at all. Is there another place closer to where you the
logic is that this code could live in?

[afakhry, 2015/06/19 17:26:54]

Deprecated accelerators are in ash. The FocusManager already has a delegate
(implemented in ash as AshFocusManagerFactory::Delegate) so that it can Process
ash accelerators (in ProcessAccelerator()) and act as the connection between
views and ash.

What do you recommend?

+
   // Resets menu key state if |event| is not menu key release.
   // This is effective only on x11.
   void MaybeResetMenuKeyState(const ui::KeyEvent& key);