
Currently, for Android users, when they set a flag in chrome://flags, they need to perform two restarts for the change to apply. A previous CL has fixed this problem for the cases where the user is setting the flag to "Enabled" or "Disabled". This is a followup CL that addresses the cases where user is setting the flag to "Default". In order to address this case, we figure out the list of flags that were enabled previously and the list of flags that are enabled now. If a flag exists in the first list but not the second, then this flag must have been set to "Default". Once we get the list of flags that have been set to "Default", we pass this list to the Java side, so that the Java side can clear the cached values associated with these flags. On the next startup, the Java side will find out that it has no cached values for these flags, so it will use the hardcoded default values. Bug: 40132529 Change-Id: Ic1f8934fcab2c7b593952c93c4a06cb6eefd2eac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6159552 Reviewed-by: Elly FJ <ellyjones@chromium.org> Reviewed-by: Henrique Nakashima <hnakashima@chromium.org> Commit-Queue: Martin Kong <martinkong@google.com> Cr-Commit-Position: refs/heads/main@{#1429048}
Chromium
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.