Contact emailssmcgr...@chromium.org, rous...@chromium.org

Specificationhttps://www.w3.org/TR/payment-method-manifest/#processing-model

Summary

Deprecate the ability for Web Payment API to bypass the connect-src CSP
policy when fetching the manifest. After this deprecation, a site's
connect-src CSP policy will need to allow for the payment method URL
specified in a PaymentRequest call, as well as any other URLs that the
method chains to fetch its manifest.

Blink componentBlink>Payments
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments>

TAG review statusNot applicable

Risks
Interoperability and Compatibility*Gecko*: N/A. Does not currently
implement or ship PaymentHandler.
*WebKit*: N/A. Does not currently implement or ship PaymentHandler.
*Web developers*: No signals

WebView application risks

None: PaymentHanlders are not supported in WebView.

Debuggability

CSP violations print console error messages.

Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?No. PaymentHandlers are not
supported on WebView.

Is this feature fully tested by web-platform-tests?No

Flag name#web-payment-api-csp

Requires code in //chrome?False

Tracking bughttps://crbug.com/1349091

Launch bughttps://crbug.com/1349093

Estimated milestones
Origin Trial first: 108
Origin Trial last: 110

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6286595631087616

Links to previous Intent discussionsIntent to prototype
<https://groups.google.com/a/chromium.org/g/blink-dev/c/jklZJYcOVyg/m/Gfwa4QQBAwAJ>
.

This intent message was generated by Chrome Platform Status
<https://chromestatus.com/>.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMMzaWFUbSFNuCbyefZKuSDmFtOd%3DD5xsOpVE0p6pwoxVPgRog%40mail.gmail.com.

Reply via email to