[Mahi] refactor: Introduce MahiUiController::State This CL introduces MahiUiController::State, corresponding to three UI states that Mahi views can stay: 1.Summary & outlines state: The views that serve summary & outlines should show. 2.Q&A state: The views that serve Q&A should show. 3.Error state: The view that visualizes the current error should show. In the subsequent CL, MahiUiController is gonna cache the current state. Because we will have UIs that rely on the current state, such as the retry link. If the current state is summary & outlines, clicking the retry link should request summary & outlines again; if the current state is Q&A, clicking the retry link should request the answer to the most recent question. This CL also moves base::ScopedObservation inside MahiUiController::Observer so that the observer subclasses do not have to create their own observations. This CL should not bring any UI difference. Bug: b/319731862 Change-Id: Iabc2f07b0dc0f0385b0169e49fc10a8e3800bcb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5407613 Reviewed-by: Andre Le <leandre@chromium.org> Commit-Queue: Andrew Xu <andrewxu@chromium.org> Cr-Commit-Position: refs/heads/main@{#1280420}
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.