ChromeBrowserInitializer offers runNowOrAfterFullBrowserStarted().
Reland of https://chromium-review.googlesource.com/c/chromium/src/+/2032049 with fixes so avoid failing ChromeCustomTabsConnectionTest (crbug.com/1048438). Instead of runNowOrAfterNativeInitialization(), the method should enqueue tasks to run when full browser starts, and not when native is started. There is a distinction - reduced mode means native is started but full browser, which includes Profiles, isn't. This fixes a crash when transitioning from reduced mode to full browser if a task that uses Profile was scheduled with runNowOrAfterNativeInitialization(). Now, it will only run after the transition, rather than immediately. Also change hasNativeInitializationCompleted() to isFullBrowserInitialized() and update clients. All but DownloadMetrics are meant to run in full browser, so that should actually revert their behavior back to what it was before reduced mode was introduced. DownloadMetrics still checks if native was loaded, which includes in reduced mode. Bug: 1045945, 1014098, 1048438 Change-Id: If99179a5720d7e550ee5653a8625021f58fc262e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037818Reviewed-by:Mohamed Heikal <mheikal@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#738370}
Showing
Please register or sign in to comment