Only check primary profile's dev tools enablement if it's managed
If the primary profile is not manged, the kDevToolsAvailability pref will default to 0 (allow, except for in force-installed extensions). This matters *only* if there's a secondary profile with a more liberal kDevToolsAvailabilityPref, because the primary profile's value would be more retrictive then. Only evaluate the primary profile's value if it is really managed. secondary profile with force-installed extensions. Set DeveloperToolsAvailability policy in the secondary profile's policy to 1 (allowed) and ensure that developer tools are usable in force-installed extensions. Bug: 924973 Test: manual -- sign-in with an unmanaged primary profile and a managed Change-Id: I1328a70664af759231ebc19bdb51a7ff1c193783 Reviewed-on: https://chromium-review.googlesource.com/c/1434316Reviewed-by:Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Lutz Justen <ljusten@chromium.org> Commit-Queue: Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#626290}
Showing
Please register or sign in to comment