LGTM1 Thanks for adding feature detection capabilities!!
On Thu, Apr 20, 2023 at 6:58 PM Nick Burris <[email protected]> wrote: > Contact [email protected], [email protected], > [email protected] > > Specificationhttps://github.com/w3c/secure-payment-confirmation/pull/233 > I see some discussion on the PR about it being approved but not yet landed, due to desire to move a previous version to PR. That seems fine, but at the same time, I join +Rick Byers <[email protected]>' request to make sure the situation doesn't last too long. Also, you may want to consider moving to a Living Standard model, that typically can avoid those kinds of issues.. > > Design docs > https://docs.google.com/document/d/10zFazJRJMwNLKmH-GJRFMDs4rONIO5kF8TvdFydmGek/edit > > Summary > > This is a Javascript API to provide an easier way to check if the Secure > Payment Confirmation[1] feature is available. Currently, the only way to > determine SPC’s availability is to create a PaymentRequest with the > required parameters[2], which is clunky and difficult in the case where a > developer wants to check for SPC before starting to process a payment. [1] > https://www.w3.org/TR/secure-payment-confirmation/ [2] > https://github.com/w3c/secure-payment-confirmation/issues/81#issuecomment-868473461 > > > 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*: N/A ( > https://github.com/mozilla/standards-positions/issues/570) > > *WebKit*: N/A (https://github.com/WebKit/standards-positions/issues/30) > > *Web developers*: Positive ( > https://github.com/w3c/secure-payment-confirmation/issues/81) We've > received feedback from web developers that an easier mechanism to check for > SPC availability would be useful. > > *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 > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?Yes > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ? > To be added to secure-payment-confirmation suite > <https://wpt.fyi/results/secure-payment-confirmation?label=experimental&label=master&aligned> > > Flag name--enable-blink-features=SecurePaymentConfirmationAvailableAPI > > Requires code in //chrome?True > > Estimated milestones > Shipping on desktop 114 > Shipping on Android 114 > Anticipated spec changes > > https://github.com/w3c/secure-payment-confirmation/pull/233 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5165040614768640 > > 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/CADvKJHOUZTzhNtVZj6bgeskfwt%2BN3YOMFTFCj5Z8nufpB3_xhw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADvKJHOUZTzhNtVZj6bgeskfwt%2BN3YOMFTFCj5Z8nufpB3_xhw%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/CAL5BFfW3XkSTdRtK06Bj%2B0bOftTWJkBMEBdx1SefphVxAxensA%40mail.gmail.com.
