commit | feaabd5cab73e6ec2debbf237becd66900d9ecb4 | [log] [tgz] |
---|---|---|
author | Federica Germinario <fedegermi@google.com> | Mon Jun 24 10:18:50 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 24 10:18:50 2024 |
tree | c1a716e3e72b7d90a038295408f60e073bbc4c91 | |
parent | 41ea221da9153cf7539b2ddb4f64e8db00d7920e [diff] |
[ios][mim] Add code to open selected profile in a new window This CL implements switchProfileButtonWasTapped by: - Updating the kBrowserStateLastUsed key - Opening a new window (creating a new scene) - Updating code in startUpChromeUI (in SceneController) to get the browserState from ChromeBrowserStateManager. Note that there is no change compared to old code in SceneController because the AppState gets the browserState in the same way. Note that this is not a final solution, but only a temporary solution that will be helpful to test some features until we have the correct APIs (and with minimal code changes outside of ../multi_identity/*). Note that: - It will be possible to test this code only on iPad since we need multi-window support. - This code opens a new window with a new sceneState associated to a browserState different from the one in the first window. It is not linked to user logged-in (so we can't test login/logout etc) Bug: 333520714 Change-Id: Ia6e51ec31392de237d8a56cd20eba6cf3d5a04ab Low-Coverage-Reason: EXPERIMENTAL_CODE Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5641336 Reviewed-by: Mark Cogan <marq@chromium.org> Commit-Queue: Federica Germinario <fedegermi@google.com> Cr-Commit-Position: refs/heads/main@{#1318492}
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.