commit | 739d3fc4830cf25624ba619d0612b4404253c861 | [log] [tgz] |
---|---|---|
author | Muyao Xu <muyaoxu@google.com> | Wed Sep 04 02:38:34 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 04 02:38:34 2024 |
tree | ae42886287131609b455495e398e8291e05656a4 | |
parent | 616eb986e6aee631c58f2b0900877064917db6a9 [diff] |
[M129] Close the Media Router device picker dialog on page closed The code to close the dialog on page destruction exists, but it failed to close the dialog because MediaRouteChooserDialogManager inaccurately shows the dialog has been closed, causing an early return in BrowserMediaRouterDialogController::closeDialog(). This CL changes the controller to always close the dialog regardless of whether the dialog is showing or not. (cherry picked from commit e51a64c9af60bddb50141a835ac32e061e81d25f) Bug: 361784548 Change-Id: If94fa9fb60c9e691564a04630730dab4dbd2bf01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5819835 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Mark Foltz <mfoltz@chromium.org> Commit-Queue: Muyao Xu <muyaoxu@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1348098} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5834036 Commit-Queue: Ahmed Moussa <ahmedmoussa@google.com> Reviewed-by: Ahmed Moussa <ahmedmoussa@google.com> Auto-Submit: Muyao Xu <muyaoxu@google.com> Cr-Commit-Position: refs/branch-heads/6668@{#823} Cr-Branched-From: 05bc664984ca075216b7f2198c88b9725bfa1b9b-refs/heads/main@{#1343869}
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.