New comments for feature: PaymentRequest
0 views
Skip to first unread message
Chromestatus
Mar 4, 2025, 3:17:54 AM3/4/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
Please request privacy/WP security/enterprise/debuggability/testing reviews, but you can mark most or all of them as N/A to the extent that the approvals on other platforms carry over.
Your next steps:
You are receiving this email because:
- You are a devrel contact for this feature.
Chromestatus
Mar 4, 2025, 10:15:47 AM3/4/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
For adding this feature to Android WebViews platform: DevTools does not have support of Android WebViews.
Web developers debug this feature through JavaScript error codes that the API returns.
WebView host app developers and payment app developers debug this feature through `adb logcat` command.
Your next steps:
Chromestatus
Mar 4, 2025, 10:19:34 AM3/4/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
Requesting WP privacy review for partially bringing the PaymentRequest API to the WebView platform. For the publicly visible privacy details, see https://w3c.github.io/payment-request/#privacy and the "Privacy Considerations" section in the public design doc https://docs.google.com/document/d/1yS2_LykHMhSTHr_oX9gtHgE8WS0x5QYtdg_k_8XBUj8.
Your next steps:
Chromestatus
Mar 4, 2025, 10:23:08 AM3/4/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
For internal privacy review, see http://launch/4328654.
Your next steps:
Chromestatus
Mar 6, 2025, 4:08:49 AM3/6/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
DevTools can remote-debug android WebViews: https://developer.chrome.com/docs/devtools/remote-debugging/webviews
Would you mind filling in the survey questions for clarity?
Your next steps:
Chromestatus
Mar 10, 2025, 1:14:31 PM3/10/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
In lieu of https://www.w3.org/TR/security-privacy-questionnaire/, please see the "Security Considerations" section in the public design doc:
https://docs.google.com/document/d/1yS2_LykHMhSTHr_oX9gtHgE8WS0x5QYtdg_k_8XBUj8/edit?tab=t.0#heading=h.4hewn7h3cigt
For internal security review, please see the "Android WebView Security" in launch/4328654.
Your next steps:
Chromestatus
Mar 10, 2025, 1:15:09 PM3/10/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
Please let me know if the provided documentation is not sufficient and the questionnaire template still needs to be filled out.
Your next steps:
Chromestatus
Mar 10, 2025, 1:18:54 PM3/10/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
(1) Does this launch include a breaking change?
No. This launch is strictly additive functionality.
(2) Is there any other reason you expect that enterprises will care about this launch?
No. Enterprises won't care about this
(3) Does your launch have an enterprise policy to control it, and will it be available when this rolls out to stable (even to 1%)?
No. A policy isn't necessary because the answer was No to the first 2 questions.
(4) Provide a brief title and description of this launch, which can be shared with enterprises.
N/A because the answer was No to the first 2 questions.
Your next steps:
Chromestatus
Mar 10, 2025, 1:39:04 PM3/10/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
Enterprise Review: No concerns from the enterprise prospective.
Approved and no mention in the release notes.
Your next steps:
Chromestatus
Mar 11, 2025, 1:10:47 PM3/11/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
(1) Does the introduction of the new Web Platform feature break Chrome DevTools' existing developer experience?
No.
(2) Does Chrome DevTools' existing set of tooling features interact with the new Web Platform feature in an expected way?
Yes.
(3) Would the new Web Platform feature's acceptance and/or adoption benefit from adding a new developer workflow to Chrome DevTools?
The answer is a resounding “it depends”.
Debugging for this launch (adding PaymentRequest API to WebView) is supported in 3 ways:
JavaScript errors returned from the PaymentRequest API.
Chrome’s, WebView host app’s, and Android native payment app’s logs in `adb logcat`.
Chrome DevTools Console, which prints some error messages from PaymentRequest API that are useful for debugging.
However, there are 2 caveats to keep in mind:
Although Chrome DevTools has ability to show the Service Worker events that are fired into the Web Payment Handler (https://w3c.github.io/payment-handler/), this launch is for Android native payment apps (https://web.dev/articles/android-payment-apps-developers-guide), which, although being shipped in Clank for almost a decade, does not have support in Chrome DevTools.
In addition, the Payment Method Manifest fetches (https://w3c.github.io/payment-method-manifest/), also implemented in Chrome for almost a decade, do not have support in Chrome DevTools. This is something that has been on our radar for the last few years (https://crbug.com/40684658), but we never got around to implementing it.
Your next steps:
Chromestatus
Mar 13, 2025, 5:57:28 AM3/13/25
to paymen...@chromium.org
Chrome Platform Status
|
|
Comment posted on feature entry: |
| PaymentRequest |
A comment was added to this feature:
The Payment Request API is designed with several security and privacy considerations and mitigations in mind [1] such as requiring transient activation on show() to prevent users sharing inadvertently sensitive info with merchants, only exposed on https, x-origins payment requests are allowed only if the merchant has authorized if the payment provider. No concerns.
[1]https://w3c.github.io/payment-request/#privacy
Your next steps:
Reply all
Reply to author
Forward
0 new messages