commit | b6cc8dbecaeeab81439ea90331bb404ef0b70655 | [log] [tgz] |
---|---|---|
author | Tomek Jurkiewicz <tju@google.com> | Thu Jun 19 17:01:25 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 19 17:01:25 2025 |
tree | 0ad097a8ea3550f17ec502a2442458a2a28fd2eb | |
parent | fb09fc1f04071fd5ced476dc2f4651219a3cf83e [diff] |
Record the local supervision type on the metrics pipeline. Records FamilyLinkUser.LogSegment and FamilyUser.WebFilterType.PerRecord for locally supervised profiles, keeping existing semantics for these metrics (see family_link_user_log_record changes). Then in order to enable testing, the supervised user service now allows injecting fake content filter observer bridges (see supervised_user_service and supervised_user_test_environment changes). Added test cases cover all combinations of {browser, content} filter settings. Recorded metrics consciously elevate existing naming debt (Family Link should not name a metric, but merely be one of possible entries) and the cleanup is backlogged for the future. Minor: adds missing imports or forward declarations, or IFTTT markers. NO_IFTTT=Updated and added new path Bug: 425685494 Low-Coverage-Reason: HARD_TO_TEST Backlogged to add missing tests Change-Id: I0cf0fa332caff3006b0375294827589652a3da40 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6647246 Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org> Commit-Queue: James Lee <ljjlee@google.com> Reviewed-by: David Roger <droger@chromium.org> Reviewed-by: James Lee <ljjlee@google.com> Cr-Commit-Position: refs/heads/main@{#1476202}
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.