Nimer - Chrome error | Stripe Developers | Page 1

junior coral May 12, 2022, 2:41 PM

#

I think that this may have something to do with crhome deprecating their basic card functionality? https://blog.chromium.org/2021/10/sunsetting-basic-card-payment-method-in.html

Chromium Blog

Sunsetting the "basic-card" payment method in the Payment Request API

The Payment Request API is a soon-to-be-recommended web standard that aims to make building low-friction and secure payment flows easier ...

chilly tide May 12, 2022, 2:44 PM

#

The payment method provided is google-pay

#

Or did I understand you incorrectly?

junior coral May 12, 2022, 3:10 PM

#

Our PaymentRequest button utilized both so there were warnings about the basic card functionality. Is this affecting your behavior or is it just a warning as far as you can tell?

chilly tide May 12, 2022, 3:13 PM

#

junior coral Our PaymentRequest button utilized both so there were warnings about the basic c...

I am using a custom button, not the 'paymentRequestButton element'. As far as I can tell this is an indication that it is not triggered by user activation (Despite being directly invoked by a buttons click event).

chilly tide May 12, 2022, 3:15 PM

#

junior coral Our PaymentRequest button utilized both so there were warnings about the basic c...

And interestingly, as this is a change from the 'paymentRequestButton element' you are referring to - I am not getting any warning from the previous implementation. Does this tell you anything?

junior coral May 12, 2022, 3:20 PM

#

So you are getting the warning when not using our payment request button but you are getting it on your own custom button?

chilly tide May 12, 2022, 3:21 PM

#

junior coral So you are getting the warning when not using our payment request button but you...

correct

#

to clarify, the custom button is using a stripe.paymentRequest.StripePaymentRequest to invoke the paymentRequest.show()

spring heath May 12, 2022, 3:58 PM

#

Just to clarify, this is a warning only and now blocking your customers from paying currently, correct?

#

The warning you shared indicates this is happening without user activation, note that .show() must be called in the event-handling chain of a user event like a click, or this might happen

#

If you are already doing that (or now using .show manually at all) then please share a code snippet showing yo integration so that we can review

chilly tide May 12, 2022, 4:13 PM

#

This is an issue, prompted by chrome under its 'issues' tab.

The warning indicates a breaking change coming up in the next version of chrome and that this current implementation as it is - which it says is not invoking the paymentRequest.show() method (to prompt the user the interactive card dialogue of google pay) through user activation (a users direct interaction with the custom stripe button) - will be removed in the coming version.

The test payments itself goes well. However, in order for me to move on with this implementation and eventually use in production - I need to clarify whether or not the next version of chrome (102) will break this implementation.

As it is now, I understand that this issue is prompted if it isn't used correctly. However, the 'paymentRequest.show()' is directly tied to a buttons click event. Without any wrapping method or similar. Which causes me to believe something is not right.

Am I making myself clear now?

spring heath May 12, 2022, 4:20 PM

#

Yes, but can you share how you are actually calling this?

#

as in, what is the code sequence by which you end up calling .show()

chilly tide May 12, 2022, 4:21 PM

#

<div...(click)="paymentRequest.show()">

#

I've also tried wrapping it in a method and invoking that method, to prevent exposing the paymentRequest publicly

#

Which I could understand would prompt such a message

#

Ah the sequence prior to this

#

?

spring heath May 12, 2022, 4:24 PM

#

can you share more code context?

#

is this in react? what else is in that div?

#

(click) is... angular?

#

Are you sure that's not being immediately invoked? I'd expect something like a function in there: (click)="() => paymentRequest.show()" or similar, not sure of the syntax

chilly tide May 12, 2022, 4:25 PM

#

Yes, it is an angular application. The div also has ngClass to conditionally apply styling (disabled/enabled)

#

No, as the issue prompted by google only comes first when I click on the button with my mouse.

#

the ...t.show() is interpreted by angular as a function

#

Which correctly and accurately opens the dialogue (with a pre-step that wasn't there before when I only had the OTS button from stripe)

#

The dialogue pre step:

#

which then takes me to this step, which with the previous button directly takes me to this step:

#

If it is noteworthy

spring heath May 12, 2022, 4:41 PM

#

OTS button
what do you mean here?

#

These two flows depend on whether you're using the default button & click or your own custom click handler, that's expected and part of the google pay implementation/limitation

chilly tide May 12, 2022, 4:46 PM

#

spring heath > OTS button what do you mean here?

your 'Off-the-shelf' button, which calls the paymentRequest.show() for you

chilly tide May 12, 2022, 4:47 PM

#

spring heath These two flows depend on whether you're using the default button & click or you...

Thank you for this clarification

#

Anything else I can share?

#

Because I still need help with my question

craggy summit May 12, 2022, 5:12 PM

#

👋 sorry @spring heath had to step away. Let me catch up here

chilly tide May 12, 2022, 5:12 PM

#

ok 👍

steep galleon May 12, 2022, 5:15 PM

#

HI 👋 I"m stepping in for @craggy summit and looking to catch up here

chilly tide May 12, 2022, 5:15 PM

#

alright

steep galleon May 12, 2022, 5:21 PM

#

Okay there's a lot going on there. Can you rephrase your initial question again (sorry for the back & forth but this stuff is tricky).

chilly tide May 12, 2022, 5:26 PM

#

I was wondering if anyone encountered a google chrome issue regarding a deprecation warning of paymentRequest.show(), for Google Pay, despite the paymentRequest.show() being directly invoked through user activation?

This is an issue, prompted by chrome under its 'issues' tab.

The warning indicates a breaking change coming up in the next version of chrome and that this current implementation as it is - which it says is not invoking the paymentRequest.show() method (to prompt the user the interactive card dialogue of google pay) through user activation (a users direct interaction with the custom stripe button) - will be removed in the coming version.

The test payments itself goes well. However, in order for me to move on with this implementation and eventually use in production - I need to clarify whether or not the next version of chrome (102) will break this implementation.

As it is now, I understand that this issue is prompted if it isn't used correctly. However, the 'paymentRequest.show()' is directly tied to a buttons click event. Without any wrapping method or similar. Which causes me to believe something is not right.

#

is this clear enough for you?

steep galleon May 12, 2022, 5:30 PM

#

Yes, this just requires some different digging on our end since your approach is non-standard and not using any of the recommended integrations. I'm looking for info about this.

#

Our inability to reproduce this error suggests there is something in the way Angular is handling the callback. Even when we force .show() calls we do not see this issue.

#Nimer - Chrome error