So this intent is requesting to run the first OT M108-M110? Any deprecation period you have in mind?
It might be better to send separate intents for the rest when their milestones get closer. On Mon, Apr 18, 2022 at 5:49 PM 'Rouslan Solomakhin' via blink-dev < blink-dev@chromium.org> wrote: > Contact emailsrous...@chromium.org > > Specificationhttps://w3c.github.io/payment-handler/ > > Summary > > This is an early heads up that we intend to remove the merchant origin and > arbitrary data from the "canmakepayment" service worker event of the > Payment Handler API. These are the event fields to be removed: > > > - topOrigin > - paymentReuqestOrigin > - methodData > - modifiers > > The removal will be happening through the use of an origin trial at first, > then a reverse origin trial, and finally removal. > Blink componentBlink>Payments > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments> > > MotivationThe “canmakepayment” service worker event lets the merchant > know whether the user has a card on file in an installed service-worker > based payment app. It silently passes the merchants’ origin and arbitrary > data to the service worker from the payment app origin. This cross-origin > communication happens on new PaymentRequest() construction in JavaScript, > does not require a user gesture, and does not show any user interface. > > Alternatively, we have considered and dismissed the option to remove the “ > canmakepayment” event entirely and behave as if it always returns "true", > because some payment app partners have indicated to us that's what they > always do. However, the data that we have collected shows that the “ > canmakepayment” event returns "false" 1% to 6% of the time, depending on > the platform. > > TAG review statusNot applicable > > Risks > Interoperability and Compatibility > > Only Chrome has implemented the Payment Handler API. > > Chrome is reaching out to the known partners that may be depending on > these fields. > > WebView application risks > > The Payment Handler API requires the use of the PaymentRequest API. > Neither API is available in WebView. > > > Is this feature fully tested by web-platform-tests > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > ?Yes > <https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/payment-handler/;drc=f539fffb79da2c97b1a06cbca88cc6d5a93ddc77> > > Flag namePaymentHandlerMerchantIdentity > > Requires code in //chrome?True > > Estimated milestones > > Origin trial: 108 > > Reverse origin trial: 111 > > Removal: 114 > > Link to entry on the Chrome Platform Status > https://chromestatus.com/feature/5190978431352832 > > 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/CAMMzaWFz1UFWxgOs%2BECSdF2Bt8JpsBkGtv2wMnq2pemGMmD8Fw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMMzaWFz1UFWxgOs%2BECSdF2Bt8JpsBkGtv2wMnq2pemGMmD8Fw%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 blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfWR1B%3DPjd_d_YG8ogVfoPdET02uMpSvV2NURH%3DAetUCzw%40mail.gmail.com.
