Make GroupedPermissionInfoBarDelegate's methods call through PermissionPromptAndroid

chrome/browser/permissions/permission_prompt_android.cc

Index: chrome/browser/permissions/permission_prompt_android.cc
diff --git a/chrome/browser/permissions/permission_prompt_android.cc b/chrome/browser/permissions/permission_prompt_android.cc
index 19631a2c5131df989b5444694d33c0aef4714ee3..3afb3d9c7f0e281303b7fc592994abae14b582a5 100644
--- a/chrome/browser/permissions/permission_prompt_android.cc
+++ b/chrome/browser/permissions/permission_prompt_android.cc
@@ -35,6 +35,10 @@ void PermissionPromptAndroid::Show(
 
   infobar_ = GroupedPermissionInfoBarDelegate::Create(
       infobar_service, requests[0]->GetOrigin(), requests);
+
+  GroupedPermissionInfoBarDelegate* infobar_delegate =
+      infobar_->delegate()->AsGroupedPermissionInfoBarDelegate();
+  infobar_delegate->SetPermissionPrompt(this);

[raymes, 2016/11/01 00:07:46]

Now that I look at it, I think passing this pointer in the constructor as you
had before is slightly better, because it means SetPermissionPrompt won't
accidentally be called multiple times.

[lshang, 2016/11/01 04:33:42]

Done.

 }
 
 bool PermissionPromptAndroid::CanAcceptRequestUpdate() {
@@ -47,6 +51,9 @@ void PermissionPromptAndroid::Hide() {
   if (infobar_ && infobar_service) {
     infobar_service->RemoveInfoBar(infobar_);
   }
+  GroupedPermissionInfoBarDelegate* infobar_delegate =
+      infobar_->delegate()->AsGroupedPermissionInfoBarDelegate();

[raymes, 2016/11/01 00:07:46]

I don't think we need to add this function, I think we can just static_cast the
infobar delegate to the GroupedPermissionInfobarDelegate because we know it will
be one of those.

[lshang, 2016/11/01 04:33:42]

Refer to other infobars, the convention seems to use a As***InfoBarDelegate() to
do the
downcasting(https://cs.chromium.org/chromium/src/components/infobars/core/infobar_delegate.h?l=213).


I don't feel strongly about it here, since we already use static_cast in
GroupedPermissionInfoBar::GetDelegate(), so proooobably it's ok?

Done.

[raymes, 2016/11/01 05:29:15]

If you know the type ahead of time (which I think in these cases we do, right?)
then a static cast is better because it avoids the virtual function call.

+  infobar_delegate->ResetPermissionPrompt();

[raymes, 2016/11/01 00:07:46]

Maybe this should just go in the destructor of this class? In terms of lifetimes
it should be safe to call as long as this class is alive, so it might make it
slightly clearer what's going on. You could also name the function
PermissionPromptDestroyed

[lshang, 2016/11/01 04:33:42]

Done.

   infobar_ = nullptr;
 }
 
@@ -69,6 +76,16 @@ void PermissionPromptAndroid::Closing() {
     delegate_->Closing();
 }
 
+void PermissionPromptAndroid::Accept() {
+  if (delegate_)
+    delegate_->Accept();
+}
+
+void PermissionPromptAndroid::Deny() {
+  if (delegate_)
+    delegate_->Deny();
+}
+
 // static
 std::unique_ptr<PermissionPrompt> PermissionPrompt::Create(
     content::WebContents* web_contents) {