Chromium Code Reviews
DescriptionMove ChromeVox loading out of ComponentLoader.
First, it isn't actually necessary to load ChromeVox from
ComponentLoader. This code is probably historical. For quite some time,
AccessibilityManager automatically loads ChromeVox on startup if the
flag is set (and automatically loads/unloads when the flag changes).
We should load it from only one place. Tested manually during startup
and when logging into a session, both work fine without this call.
Second, I intend to refactor AccessibilityManager so that it can support
multiple accessibility component extensions. Rather than a separate function
in ComponentLoader to load each one, I think it'd make more sense for
AccessibilityManager to just call ComponentLoader with the appropriate
parameters like the extension id and path.
BUG=634233
Committed: https://crrev.com/18f89cf0b120afff95e064f437140bdbfb33ef36
Cr-Commit-Position: refs/heads/master@{#409916}
Patch Set 1 #
Total comments: 2
Patch Set 2 : AddComponentWithGuestManifest #
Total comments: 2
Patch Set 3 : Rename to AddComponentFromDir #
Messages
Total messages: 17 (8 generated)
|
|||||||||||||||||||||||||||||||||||||