| commit | 48e7faaff0bf2007694a9325a6b1c0ffbefcb0d9 | |
| author | bartfab <bartfab@chromium.org> | |
| Fri, 24 Oct 2014 13:50:56 +0000 (24 06:50 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 24 Oct 2014 13:51:21 +0000 (24 13:51 +0000) | ||
| tree | 22120946bb3a21c23ee100d4d136bfa0d94c3e33 | treesnapshot (tar.gz zip) |
| parent | d0f72112a76c7b3449875478fce65f7d0b4b98e9 | commitdiff |
Add device disabling to OOBE flow
Chrome OS retrieves device state from DMServer during OOBE. If this
state indicates that the device should be disabled, it will show a
corresponding screen and prevent the user from proceeding further.
The feature is on by default because we are aiming for M40 but a flag
is provided that can easily be flipped to turn it off if we do not
make the deadline.
BUG=425574
TEST=Unit and browser tests
Review URL: https://codereview.chromium.org/676773002
Cr-Commit-Position: refs/heads/master@{#301092}
Chrome OS retrieves device state from DMServer during OOBE. If this
state indicates that the device should be disabled, it will show a
corresponding screen and prevent the user from proceeding further.
The feature is on by default because we are aiming for M40 but a flag
is provided that can easily be flipped to turn it off if we do not
make the deadline.
BUG=425574
TEST=Unit and browser tests
Review URL: https://codereview.chromium.org/676773002
Cr-Commit-Position: refs/heads/master@{#301092}
22 files changed: