Android: Move BrowserControlsManager to RootUiCoordinator
This CL lets RootUiCoordinator create and provide BrowserControlsManager to other classes. Chrome*Activity still has #getBrowserControlsManager which now just defers the call to RootUiCoordinator. This makes |createComponent| and |createRootUiCoordinator| in ChromeActivity#performPreInflationStartup form dependencies on each other for CCT/Webapp. This was broken by creating RootUiCoordinator first and having some components be passed to it as a supplier instead. Bug: 966272 Change-Id: Ic89fdb77d0886d448033599c9e20128c96f071c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2327351 Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Reviewed-by:Matthew Jones <mdjones@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Cr-Commit-Position: refs/heads/master@{#798869}
Showing
Please register or sign in to comment