#paymentplugins-googlepay-bug
scarlet parcel
Not sure but if you have detailed information I can flag to some engineers internally
thorny arrow
@scarlet parcel Sounds good thank you. Here are the details: In the this.paymentsClient.createButton function, a JSON object of button properties can be passed. The GPay button supports several buttonType options including a "buy", "pay", "checkout", "subscribe" option which affects the text that appears on the GPay button that's rendered. If any buttonStyle other than "buy" is passed, a JS error is being triggered because the pay.js script is not handling the buttonStyle property correctly.
On the GPay demo site, you can observe the issue. If you select a ButtonType of "pay" for example, the button won't render. https://developers.google.com/pay/api/web/guides/resources/customize
scarlet parcel
does it happen on Stripe too? Like we support that functionality
oh boy
do you have a public report somewhere? They take bug report publicly seriously
thorny arrow
I have not observed this with the Payment Request Button integration. It appears to just be related to the pay.js script which I don't believe Stripe uses in the backend.
Or if Stripe does use the pay.js script, I believe yall just pass the "buy" buttonStyle prop which isn't affected by this bug.
Here is a public report: https://wordpress.org/support/topic/urgent-cannot-read-properties-of-undefined-reading-pay/
scarlet parcel
that's not really a public report to google though
thorny arrow
I am not aware of how to submit a public report to Google. The details are somewhat cryptic on how to go about that.
scarlet parcel
ack, just asking if you did a public report
thorny arrow
If you have any info on how to submit a public report, much appreciated.
scarlet parcel
I don't but I'm asking internally
thorny arrow
@scarlet parcel thank you
scarlet parcel
Okay no promises but we have our own contacts and are reaching out to flag