Restart browser after Chromad enrollment
The current factoring of BrowserPolicyConnectorChromeOS only allows to swap out the device policy provider at initialization time, not at run time. As a consequence, we end up with the wrong device policy provider after Chromad enrollment. A browser restart is the easiest way to fix this. BUG=681817 Review-Url: https://codereview.chromium.org/2842163002 Cr-Commit-Position: refs/heads/master@{#468592}
Showing
Please register or sign in to comment