On Mon, Apr 17, 2023 at 9:42 PM Nick Burris <[email protected]> wrote:
> Contact [email protected], [email protected], > [email protected] > > Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/236 > > Design docs > https://docs.google.com/document/d/1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNxcHgfMXVwA > > Summary > > To help developers reduce friction in Secure Payment Confirmation flows, > we are removing the user activation requirement. Spam and clickjacking > mitigations are put in place to mitigate security and privacy risks with > this change (see design doc > <https://docs.google.com/document/d/1DW4hGyuVzcN8sE8TC3YOkg6xO4XpUGZQNxcHgfMXVwA> > ). > > > Blink componentBlink>Payments > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments> > > TAG reviewNone > > TAG review statusNot applicable > > Risks > Interoperability and Compatibility*Gecko*: No signal > > *WebKit*: No signal > Have we asked for a signal? Are they shipping this feature? > > *Web developers*: We've received direct feedback from web developers that > they would be able to reduce friction in their redirect-based payment flows > if SPC could be initiated without a user activation. > > *Other signals*: > > WebView application risks > > Does this intent deprecate or change behavior of existing APIs, such that > it has potentially high risk for Android WebView-based applications? > > None > > > Debuggability > > Existing debuggability for SPC; e.g. a specific SecurityError is thrown > when an activationless show() call is not allowed (see this test page > <https://rsolomakhin.github.io/pr/spc-activationless/>). > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?No, only features where > SPC is already shipped: Windows, Mac, Android > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?Yes > <https://wpt.fyi/results/secure-payment-confirmation/authentication-requires-user-activation.https.html?label=experimental&label=master&aligned> > (to > be updated with implementation) > > Flag name > --enable-blink-features=SecurePaymentConfirmationActivationlessShow > > Requires code in //chrome?False > > Estimated milestones > Shipping on desktop 114 > Shipping on Android 114 > > Anticipated spec changes > https://github.com/w3c/secure-payment-confirmation/pull/236 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5197059260416000 > > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADvKJHN9Rp4gYYZJ4Jx9iwMiA3jS%2BagC_7L5dWkEGrWo8OLX4w%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADvKJHN9Rp4gYYZJ4Jx9iwMiA3jS%2BagC_7L5dWkEGrWo8OLX4w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfXGu%3DXZYfjBcgNbkKFaT9Q%2BaqX6SzRRx25LS7ZrA1p3tg%40mail.gmail.com.
