Ensure that the Profile menu behaves appropriately in PWAs
When selecting a profile from the Profiles menu, it may be necessary to load that profile. ExtensionAppShimHandler currently goes through the hoops to do that in OnShimProcessConnected->OnProfileLoaded-> OnExtensionEnabled. Generalize that path into a LoadProfileAndApp function that will make callback with a Profile* and Extension*. Use the LoadProfileAndApp in both OnShimProcessConnected and OnShimSelectedProfile. When in multi-profile mode, no longer specify a valid Profile to the AppShimHost. Clean up the places where the AppShimHost's profile path was used, to avoid using the profile path. Change the app shim to specify its full path (instead of a relative path), and remove the GetFullProfilePath and ProfileExistsForPath delegate functions. And add some tests for all of this. Bug: 982024 Change-Id: Icb1e7c688cea67758d9d0236856c8f6b612c1cd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1825926 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#700879}
Showing
This diff is collapsed.
Please register or sign in to comment