#Tices
brisk totem
kind sphinx
Are you able to reliably reproduce the behavior? Or does it still seem random?
uneven acorn
I haven't been able to reproduce the issue locally or on the production server, but the affected customers run across the issue on multiple browsers on the same device.
Unfortunately I don't have console logs from those customers.
kind sphinx
Do you know with certainty that they are using updated versions of the browsers?
here are the requirements for stripe.js elements (like the Card Element) to show up: https://stripe.com/docs/js/appendix/supported_browsers
uneven acorn
They were running Chrome and Safari but I'm not sure what version. To my knowledge these issues started on the 19th of last month and now I'm getting a couple of these a week across a couple websites using slightly different integrations. So it feels like something changed. Is there a way to get an error response out of the mount method so that I can log that reponse? I see there is a loaderror handler but it doesn't seem to work with the card element.
kind sphinx
Hmmm, let me check internally to see if I missed something crucial
Will circle back in a few
uneven acorn
Thanks, I appreciate the help.
kind sphinx
This seems to boil down to "how can we figure out why mount() is failing` right?
Mostly it sounds like the CardElement isn't appearing/mounting and you need help tracking why.
It doesn't look like we have a way, we don't fire an error like we do for PaymentElement where it doesn't load.
I'd say the best most going forward would be to implement client-side exception handling like Sentry and such to track what's happening.
And if not, you'll want work with one of those customers to look at the JS console in the browser and see if there are any obvious errors