#codelogix

1 messages · Page 1 of 1 (latest)

tiny acornBOT
crystal nest
#

hey again, do you have more you can share about this? I'd asked previously how this was surfaced to you.

#

Is this blocking your payments with Stripe/PRB?

opal oxide
#

Yes it is blocking some users from making a payment at all.

crystal nest
#

Are you able to reproduce it reliably?

opal oxide
#

I guessing that the input shouldn't be rendered outside of the iframe if it's being loaded from Stripe

#

No. The problem is that sometimes the maxlength validation is breaking our form validation and sometimes it's not.

crystal nest
#

breaking our form validation

#

You own custom form?

#

Can you explain how that relates to the PRB integration?

opal oxide
#

We load the payment request button on our form and we have JS that checks for form elements that have validation errors...and because this field is rendered outside of the iframe, and sometimes it's invalid(i.e has validation errors), it's being caught by our form validation logic and blocking users from making a payment.

#

This error has come up 981 times today...that's almost a thousand payments that have been blocked by this.

#

Can you escalate this issue?

crystal nest
#

Trying to get an understand of this to determine next actions, yep

#

So the issue is in your own form validation? ie, if you disable that, there are no issues with the PRB?

opal oxide
#

Correct...but the PRB shouldn't be rendering an input outside of the iframe that renders the PRB.

crystal nest
#

Can you exclude the PRB input from your validation? ie, based on the __PrivateStripeElement-input class?

opal oxide
#

Do you know why this input is being rendered outside of the iframe? and what it's used for?

crystal nest
#

I don't know that off the top of my head. To your knowledge, this is new behaviour though?

#

ie, you're only seeing this recently?

opal oxide
#

Yeah...seems like this started when Apple made the change to allow ApplePay in Chrome, not sure when that was...we're seeing the error significantly more in chrome vs safari, but it still happens in both. Maybe an 90/10 split chrome/safari.

crystal nest
#

Ok so I confirmed this is not new, the input element outside the iframe has been use for much longer than the ios16 change

#

Without getting into to much detail, we use this to help control focus on inputs etc

#

I'm not saying there isn't an issue, only that the input you're pointing to is not new

opal oxide
#

Got it. Thank you that is helpful context. I appreciate you digging into this for us. I have a fix for our validation that will exclude this element in the check, which should fix the issue for us.

#

Have a great rest of your day.

#

Can you please archive this thread so it cannot be viewed?

crystal nest
#

I can archive it, but it will still be viewable

#

You can delete any messages you'd like, though

opal oxide
#

👍

crystal nest
#

And no problem, appreciate your patience while i was testing & researching. I'm glad to hear you've got an exception in place that does what you need.

#

Please don't hesitate to reach out if you're still having issues

opal oxide
#

Will do. 🙂

#

Quick question:

#

Do you know if there is a wallpaper like the profile image?

image.png
crystal nest
#

Not exactly, but sort of 😉

#

then resize as needed, but its fairly high res

opal oxide
#

Nice! Thanks!

crystal nest
#

Then its a game of waiting for a pattern you like 😄

#

NP

opal oxide
#

lol

crystal nest
#

Are you familiar with the Konami code?

opal oxide
#

Yeah

crystal nest
#

try that 😉

opal oxide
#

that's pretty cool

crystal nest
#

Have fun with it, and good luck with the rest of your work. Archiving...