commit | 4c153b44a34e480253e99276217b766b8f78193f | [log] [tgz] |
---|---|---|
author | Chad Duffin <chadduffin@chromium.org> | Thu Mar 07 22:40:09 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 07 22:40:09 2024 |
tree | 6d7046a89c8535437f42d09fafa11e3a71f67ca0 | |
parent | 9b6d2c3d233abf81f2655885487b581defe7b418 [diff] |
cellular: Refresh installed profiles This change updates the "add eSIM" dialog to refresh the installed profiles immediately when opened. This preserves the behavior of the dialog when the SM-DS Support feature flag is disabled; this discrepancy arose after we made the dialog require manual consent to perform an SM-DS scan, and the previous SM-DS scan internally refreshed the installed profile list. Manual test steps: + Open "add eSIM" dialog + Observe we immediately start refreshing profile list + Skip to manual entry + Enter eSIM profile information + Begin installation before refreshing finishes + Observe that we continue refreshing profile list, and afterwards begin installing the eSIM profile (cherry picked from commit a71632b14b9e244c7e0c8cb2ad29dec32a74b1db) Bug: b/326163082 Test: Manually on device and unit tests. Change-Id: I99ce51ea434d6de74a806279e210844d6764c684 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5325139 Commit-Queue: Chad Duffin <chadduffin@chromium.org> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by: Chris Bookholt <bookholt@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1266728} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5352450 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Cr-Commit-Position: refs/branch-heads/6312@{#459} Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}
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.