PaymentRequest.canMakePayment() query quota on desktop.

chrome/browser/payments/payment_request_factory.h

 // Copyright 2016 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.
 
 #ifndef CHROME_BROWSER_PAYMENTS_PAYMENT_REQUEST_FACTORY_H_
 #define CHROME_BROWSER_PAYMENTS_PAYMENT_REQUEST_FACTORY_H_
 
 #include "components/payments/mojom/payment_request.mojom.h"
 #include "mojo/public/cpp/bindings/binding.h"
 #include "services/service_manager/public/cpp/bind_source_info.h"
 
 namespace content {
+class RenderFrameHost;
 class WebContents;
 }
 
 namespace payments {
 
-// Will create a PaymentRequest attached to |web_contents|, based on the
-// contents of |request|. This is called everytime a new Mojo PaymentRequest is
-// created.
-void CreatePaymentRequestForWebContents(
-    content::WebContents* web_contents,
-    const service_manager::BindSourceInfo& source_info,
-    payments::mojom::PaymentRequestRequest request);
+// Will create a PaymentRequest attached to |render_frame_host| and the

[Mathieu, 2017/05/08 15:28:11]

can you modify your comment to explain to future readers what's the relationship
between render_frame_host and web_contents. "attached" and "associated" are
pretty vague, especially in the context of iframes. 

[please use gerrit instead, 2017/05/08 17:28:47]

Done, I think? Sorry, explaining complex concepts succinctly is difficult. Let
me know if you have better suggestions for wording.

+// associated |web_contents|, based on the contents of |request|. This is called
+// everytime a new Mojo PaymentRequest is created.
+void CreatePaymentRequest(content::RenderFrameHost* render_frame_host,
+                          content::WebContents* web_contents,
+                          const service_manager::BindSourceInfo& source_info,
+                          mojom::PaymentRequestRequest request);
 
 }  // namespace payments
 
 #endif  // CHROME_BROWSER_PAYMENTS_PAYMENT_REQUEST_FACTORY_H_