[Bedrock] Move SigninViewController to BrowserWindowFeatures This CL moves SigninViewController off Browser and into BrowserWindowFeatures. Stored Profile*, TabStripModel* and BrowserWindowInterface* as member variables in SigninViewController instead of browser. BrowserWindowInterface was necessary as member variable because: 1. SigninViewController code calls Navigate which needs Browser. 2. SigninViewController code also calls various other classes which need Browser too. Moving 1 off Browser is being tracked separately. Moving 2 off Browser will be also be tracked as a future follow up. TearDownPreBrowserViewDestruction function was added in SigninViewController to handle some browser test failures. And CloseModalSignin call was moved into that. Previously the browser tests depended on receiving OnBrowserRemoved message from Browser destruction before SigninViewController was destroyed to ensure "browser-is-valid". With this refactoring SigninViewController is destroyed before that message is sent. So, an explicit TearDownPreBrowserViewDestruction call is necessary. TearDownPreBrowserViewDestruction is now called deterministically from BrowserWindowFeatures::TearDownPreBrowserViewDestruction(). It is also called from BrowserWithTestWindowTest::TearDown to handle issues with some unit tests. A nogncheck was added to resolve a circular dependency problem and a tracking bug was created to fix it later. Also opportunitistically made some variables const. Bug: 418802319 Change-Id: Id0db9f9446bfeef69fb4cd73a1b70d978a529687 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6604286 Reviewed-by: Lei Zhang <thestig@chromium.org> Reviewed-by: Tom Lukaszewicz <tluk@chromium.org> Commit-Queue: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1472804}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.