Fix extension_info.mayDisable flag
Chrome management API (used, for example, by Chrome Web Store) sets mayDisable flag according to whether requesting extension has access to modify settings of requested one, but not that requested one can be disabled at all (eg. if it is extension from force list, it should always remain enabled). This commit fixes this behavior. Also this commit fixes ExtensionManagementApiTest.ManagementPolicyProhibited test: when supplying PROHIBIT_MODIFY_STATUS to TestManagementPolicyProvider is't better to specify why status modification is prohibited. Bug: 954144 Change-Id: Iaa4a31502dffca45b3d7eca3def56d3281a796e0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1823873 Commit-Queue: Oleg Davydov <burunduk@chromium.org> Reviewed-by:Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Ivan Šandrk <isandrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#704115}
Showing
Please register or sign in to comment