ChromeReportingExtension Policies definition is not accurate. |
||
Issue descriptionFour ChromeReportingExtension Policies ReportVersionData, ReportPolicyData, ReportMachineIDData and ReportUserIDData say they are not a Per Profile policy. However, the associated prefs are registered in the Profile. https://cs.chromium.org/chromium/src/chrome/browser/extensions/api/enterprise_reporting_private/prefs.cc?type=cs&sq=package:chromium&g=0&l=21&q=RegisterProfilePrefs
,
Oct 30
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8e27b63805a1ebf816a3909736c919f66080fc7e commit 8e27b63805a1ebf816a3909736c919f66080fc7e Author: Nicolas Ouellet-payeur <nicolaso@chromium.org> Date: Tue Oct 30 14:44:36 2018 Chrome Reporting: mark policies as per-profile policies Bug: 898675 Change-Id: I30ade484ed47cb2254eba66cc7ac8fc69a26bb47 Reviewed-on: https://chromium-review.googlesource.com/c/1299273 Reviewed-by: Owen Min <zmin@chromium.org> Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#603894} [modify] https://crrev.com/8e27b63805a1ebf816a3909736c919f66080fc7e/components/policy/resources/policy_templates.json
,
Oct 30
|
||
►
Sign in to add a comment |
||
Comment 1 by zmin@chromium.org
, Oct 24