|
|
DescriptionPreviously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own).
Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked.
BUG=640885
Committed: https://crrev.com/2ed22bdcbf5985dbfe4c2e5cafa12b5ef851f77e
Cr-Commit-Position: refs/heads/master@{#417576}
Patch Set 1 #
Total comments: 2
Patch Set 2 : Addressed comment #
Messages
Total messages: 27 (17 generated)
The CQ bit was checked by mahmadi@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Description was changed from ========== Disables user manager actions only if there is at least one regular profile and they're all locked. BUG=640885 ========== to ========== Previously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own). Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked. BUG=640885 ==========
mahmadi@chromium.org changed reviewers: + anthonyvd@chromium.org
Hi Anthony, Please take a look at this CL.
lgtm % small nit https://codereview.chromium.org/2325643003/diff/1/chrome/browser/profiles/pro... File chrome/browser/profiles/profiles_state.h (right): https://codereview.chromium.org/2325643003/diff/1/chrome/browser/profiles/pro... chrome/browser/profiles/profiles_state.h:109: bool AreAllProfilesLocked(); nit: can this be renamed to something more descriptive of what it does after this change?
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by mahmadi@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Thanks! https://codereview.chromium.org/2325643003/diff/1/chrome/browser/profiles/pro... File chrome/browser/profiles/profiles_state.h (right): https://codereview.chromium.org/2325643003/diff/1/chrome/browser/profiles/pro... chrome/browser/profiles/profiles_state.h:109: bool AreAllProfilesLocked(); On 2016/09/08 14:27:54, anthonyvd wrote: > nit: can this be renamed to something more descriptive of what it does after > this change? Done.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
The CQ bit was checked by mahmadi@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from anthonyvd@chromium.org Link to the patchset: https://codereview.chromium.org/2325643003/#ps20001 (title: "Addressed comment")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
mahmadi@chromium.org changed reviewers: + rogerta@chromium.org
rogerta@ please review c/b/ui/webui/signin/
lgtm
The CQ bit was checked by mahmadi@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Description was changed from ========== Previously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own). Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked. BUG=640885 ========== to ========== Previously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own). Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked. BUG=640885 ==========
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== Previously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own). Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked. BUG=640885 ========== to ========== Previously, User manager actions were being disabled if no regular (aka custodian) profiles existed (b/c it's not possible to have a supervised profile on its own). Since it's possible for child profiles to exist on their own, this CL changes the behavior so that user manager actions are disabled only if there is at least one regular profile and that all regular profiles are locked. BUG=640885 Committed: https://crrev.com/2ed22bdcbf5985dbfe4c2e5cafa12b5ef851f77e Cr-Commit-Position: refs/heads/master@{#417576} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/2ed22bdcbf5985dbfe4c2e5cafa12b5ef851f77e Cr-Commit-Position: refs/heads/master@{#417576} |