Implement app banner info bars on desktop.

chrome/browser/android/banners/app_banner_data_fetcher_android.cc

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/android/banners/app_banner_data_fetcher_android.h"
 
 #include "chrome/browser/android/banners/app_banner_infobar_delegate_android.h"
+#include "chrome/browser/infobars/infobar_service.h"
 #include "chrome/browser/ui/android/infobars/app_banner_infobar_android.h"
 #include "third_party/skia/include/core/SkBitmap.h"
 
 namespace banners {
 
 AppBannerDataFetcherAndroid::AppBannerDataFetcherAndroid(
     content::WebContents* web_contents,
     base::WeakPtr<Delegate> weak_delegate,
     int ideal_icon_size)
     : AppBannerDataFetcher(web_contents, weak_delegate, ideal_icon_size) {
@@ skipping 41 matching lines @@
       RecordDidShowBanner("AppBanner.WebApp.Shown");
   } else {
     scoped_ptr<AppBannerInfoBarDelegateAndroid> delegate(
         new AppBannerInfoBarDelegateAndroid(
             event_request_id(), title, new SkBitmap(*icon), native_app_data_,
             native_app_package_));
     infobar = new AppBannerInfoBarAndroid(delegate.Pass(), native_app_data_);
     if (infobar)
       RecordDidShowBanner("AppBanner.NativeApp.Shown");
   }
+  InfoBarService::FromWebContents(web_contents)
+      ->AddInfoBar(make_scoped_ptr(infobar));
 
   return infobar;

[benwells, 2015/06/02 05:53:35]

Is there any reason to return infobar now? It feels weird to pass ownership of
it on to InfoBarService and then return a raw pointer.

Also as this function is showing the banner, maybe it should be called
ShowBanner instead of just CreateBanner?

[dominickn (DO NOT USE), 2015/06/02 06:51:32]

Done. 
There is already a ShowBanner function which sends a message to the renderer
asking if it's okay to show the banner. I can rename that function to
RequestShowBanner.

 }
 
 }  // namespace banners