Include component extensions when initializing extension-controlled prefs.
As of https://crrev.com/170137, component extensions/apps are installed when their version changes, performing all the usual extension-install work, including registering the extension with ExtensionPrefValueMap. When a component extension is loaded without a version change, much of this is skipped, leading to ExtensionPrefValueMap::CanExtensionControlPref() hitting a NOTREACHED(). Fix this by including component extensions when initializing extension-controlled prefs, which includes registering the extension with ExtensionPrefValueMap. Bug: 454513 Change-Id: Ic478e5ac5367e3bb22cebd6e9422e9ca5bd48849 Reviewed-on: https://chromium-review.googlesource.com/897223Reviewed-by:Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Commit-Queue: Sam McNally <sammc@chromium.org> Cr-Commit-Position: refs/heads/master@{#577380}
Showing
Please register or sign in to comment