cros: Move ChromeVoxPanel bounds management into ash
ChromeVoxPanel depends on knowledge of fullscreen state and docked magnifier state in order to compute its bounds. In addition it can update the window manager's work area. Under go/mustash this knowledge lives in the ash process, not in the browser. Therefore move the bounds and work area management into ash. Next steps include introducing a mojo interface for setting the ChromeVox panel's fullscreen state and moving AccessibilityObserver support to ash::AccessibilityController from the system tray code. Bug: 628655, 819351 Test: added to ash_unittests Change-Id: Ibb27a0b8ab6b998ecd305b7e7bfbad8b35853613 Reviewed-on: https://chromium-review.googlesource.com/952263 Commit-Queue: James Cook <jamescook@chromium.org> Reviewed-by:Michael Wasserman <msw@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#541614}
Showing
Please register or sign in to comment