Start banner pipeline immediately after navigating, if enough engagement

chrome/browser/banners/app_banner_manager.cc

Index: chrome/browser/banners/app_banner_manager.cc
diff --git a/chrome/browser/banners/app_banner_manager.cc b/chrome/browser/banners/app_banner_manager.cc
index d60e013bc216402d065ec97ab526b5f66640a69c..ea650feb6c9889ab7f9736c4f13220a062f63f56 100644
--- a/chrome/browser/banners/app_banner_manager.cc
+++ b/chrome/browser/banners/app_banner_manager.cc
@@ -428,8 +428,13 @@ void AppBannerManager::DidFinishLoad(
   // If the bypass flag is on, or if we require no engagement to trigger the
   // banner, the rest of the banner pipeline should operate as if the engagement
   // threshold has been met.
-  if (AppBannerSettingsHelper::HasSufficientEngagement(0))
+  // Additionally, if the page already has enough engagement, trigger the
+  // pipeline immediately.
+  if (AppBannerSettingsHelper::HasSufficientEngagement(0) ||
+      AppBannerSettingsHelper::HasSufficientEngagement(
+          GetSiteEngagementService()->GetScore(validated_url))) {
     has_sufficient_engagement_ = true;
+  }
 
   // Start the pipeline immediately if we pass (or bypass) the engagement check,
   // or if the feature to run the installability check on page load is enabled.