Reland: Proposed alternative for supporting ChromeVox keyboard commands.
commitfd78e00559a09b91995e5c7df0d34e5ff8173a3d
authordtseng <dtseng@chromium.org>
Fri, 26 Jun 2015 00:03:48 +0000 (25 17:03 -0700)
committerCommit bot <commit-bot@chromium.org>
Fri, 26 Jun 2015 00:06:12 +0000 (26 00:06 +0000)
tree7e132cf6525f60f4901928971a692f4d1064c258
parenta281547280197998ca669bbd4a107fca1d6e1ed5
Reland: Proposed alternative for supporting ChromeVox keyboard commands.

Original change:
https://codereview.chromium.org/1185753008/

This change avoids the use of ProfileManager::GetLastUsedProfile by asking AccessibilityManager directly which profile it is using. Since AccessibilityManager is the authority on which profile spoken feedback is running, this is a safe and probably better change

TEST=ensure chrome.commands.onCommand gets called with appropriate command name when keys are struck on OOBE, locked screen, login screen, and logged in.
TBR=oshima@chromium.org

Review URL: https://codereview.chromium.org/1209073002

Cr-Commit-Position: refs/heads/master@{#336299}
chrome/browser/chromeos/accessibility/accessibility_manager.h
chrome/browser/chromeos/accessibility/spoken_feedback_event_rewriter.cc [new file with mode: 0644]
chrome/browser/chromeos/accessibility/spoken_feedback_event_rewriter.h [new file with mode: 0644]
chrome/browser/chromeos/accessibility/spoken_feedback_event_rewriter_unittest.cc [new file with mode: 0644]
chrome/browser/chromeos/chrome_browser_main_chromeos.cc
chrome/chrome_browser_chromeos.gypi
chrome/chrome_tests_unit.gypi