Activate ARCVM on policy change remote install ARC on demand delays activating ARCVM so that ARC may not be activated when remote installs are triggered. Currently ARC on demand will only be enabled when the user is a managed account and there are no apps installed on the device (see arc_activation_necessity_checker.cc). This CL adds handling for remote force install on admin policy change. BUG=b:242832961 TEST=autoninja -C out/Default ash_components_unittests && out/Default/ash_components_unittests TEST=Manual testing on DUT with/without ARC on Demand, changing the policy by changing app to force install/allow install. Change-Id: I03f418f2145546e8192f1d06187a7ff636fd15f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4115050 Reviewed-by: Yao Li <yaohuali@google.com> Commit-Queue: Bryan Yu <yuholong@google.com> Code-Coverage: Findit <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1102097}
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.