diff options
| author | bartfab@chromium.org <bartfab@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-11 12:52:50 +0000 |
|---|---|---|
| committer | bartfab@chromium.org <bartfab@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-11 12:52:50 +0000 |
| commit | 681d053f56e8811feebe868953722617e0ea1377 (patch) | |
| tree | 98d5f1fe8ace03e4f81107da0869186798839887 /components/user_prefs | |
| parent | 314231525aea6fa7480cff1f3adccfbe6f5f960d (diff) | |
| download | chromium_src-681d053f56e8811feebe868953722617e0ea1377.zip chromium_src-681d053f56e8811feebe868953722617e0ea1377.tar.gz chromium_src-681d053f56e8811feebe868953722617e0ea1377.tar.bz2 | |
Stop passing the OOBE WebUI object to AccessibilityManager
When enabling spoken feedback on an OOBE screen, ChromeVox needs to be
injected into the screen's WebUI. The AccessibilityManager expects the
caller to determine whether an OOBE screen is being shown and if so, to
pass in a pointer to its WebUI.
This has led to many different code paths trying to determine the OOBE
WebUI, all doing it slightly differently. Many code paths do not even try
at all, passing in NULL unconditionally.
This CL moves the logic that determines whether an OOBE screen is being
shown into the AccessibilityManager, removing the need to pass a WebUI
object to it.
BUG=225956
TEST=browser and unit tests updated + manual in VM
TBR=jam (testing_automation_provider_chromeos.cc)
TBR=nkostylev (tray_accessibility_browsertest.cc + core_oobe_handler.cc)
TBR=derat (chrome_shell_delegate_chromeos.cc)
Review URL: https://chromiumcodereview.appspot.com/16570002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@205516 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'components/user_prefs')
0 files changed, 0 insertions, 0 deletions