[Extensions] Account for policy-blocked extensions in ExtensionEnableFlow
ExtensionEnableFlow tries to re-enable a disabled extension, but did not account for extensions that cannot be re-enabled by enterprise policy. This would result in the ExtensionEnableFlow trying to re-enable the extension (which would fail), and then notifying the delegate that the re-enable was successful (which it wasn't). This could lead to an infinite loop in the app list, where an ExtensionAppItem would try to launch, see the extension needed to be re-enabled, try to re-enable the extension through the ExtensionEnableFlow, see that it was successful, and try to launch. Fix this by checking if the extension must remain disabled in the ExtensionEnableFlow and responding appropriately. Add a regression test for the same. Bug: 783831 Change-Id: I53cddecc895a9602f0884fa022b68ea7a6c2d667 Reviewed-on: https://chromium-review.googlesource.com/764851 Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Reviewed-by:Karan Bhatia <karandeepb@chromium.org> Cr-Commit-Position: refs/heads/master@{#516309}
Showing
Please register or sign in to comment