Revert "Reland "[Clank CBCM] Disable UMA controls on pre-MICe FRE when policy disables metrics"" This reverts commit 3e8996c301a479638e75b5a27c35da7ad32fa12d. Reason for revert: Suspected culprit for crbug.com/1296096 Original change's description: > Reland "[Clank CBCM] Disable UMA controls on pre-MICe FRE when policy disables metrics" > > This is a reland of 8ba1895fdd432eddd9ad5cb93768819795d16e57 > > Original change's description: > > [Clank CBCM] Disable UMA controls on pre-MICe FRE when policy disables metrics > > > > This implementation follows go/clank-metricsreportingenabled-design document. > > > > This change waits for Native to check the status of MetricsReportingEnabled then updates UI state accordingly. After this, we don't respond to changes in the policy. (I.E. CBCM as explicitly stated in design doc). > > > > For non-enterprise/policy users we don't need nor wait for Native to have a working interface, and for enterprise/policy users we've already waited for Native to be initialized so this does not affect the FRE initial latency. > > > > Screenshots. > > Pre-MICe FRE, MetricsReportingEnabled=True: https://storage.cloud.google.com/chromium-translation-screenshots/29724b42919ebef8bfc95b6ccfd577d1a6978db2 > > Pre-MICe FRE with Uma Dialog, MetricsReportingEnabled=True: https://storage.cloud.google.com/chromium-translation-screenshots/2580f9dae2d96206fbc72277d4a4489984d7a415 > > > > Pre-MICe FRE, MetricsReportingEnabled=False: https://storage.cloud.google.com/chromium-translation-screenshots/da76256b07cd7175e06a573fe8ed492b00642a0b > > Pre-MICe FRE with Uma Dialog, MetricsReportingEnabled=False: https://storage.cloud.google.com/chromium-translation-screenshots/552c13ae75269c5827b84afbafc9c96b4965c90d > > > > Bug: 878558 > > Change-Id: I7c91d4524a788b50e994c24f6ca987ad001ada0e > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3385621 > > Reviewed-by: Fabio Tirelo <ftirelo@chromium.org> > > Reviewed-by: Filip Gorski <fgorski@chromium.org> > > Reviewed-by: Sky Malice <skym@chromium.org> > > Commit-Queue: Og Astorga <ogastorga@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#965517} > > Bug: 878558 > Change-Id: I2395e554dc876ff7b1717cd0d2c8d5ca9a0e77da > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3440718 > Reviewed-by: Filip Gorski <fgorski@chromium.org> > Commit-Queue: Og Astorga <ogastorga@chromium.org> > Cr-Commit-Position: refs/heads/main@{#969288} Bug: 878558, 1296096 Change-Id: I9cdcabebf6342705d55d6f0eef3a8feb8ba64935 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3451721 Auto-Submit: Andrey Zaytsev <andzaytsev@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Andrey Zaytsev <andzaytsev@google.com> Owners-Override: Andrey Zaytsev <andzaytsev@google.com> Cr-Commit-Position: refs/heads/main@{#969385}
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.