#Matty - Payment Element
1 messages ยท Page 1 of 1 (latest)
Indeed there is. Here's the documentation: https://stripe.com/docs/js/element/events/on_change?type=paymentElement
How the heck did I miss that??? ๐ Thank you!
Happy to help ๐
Random question: This spacing shows up when we set the billingDetails.address to 'never'. Is there a way to remove that spacing?
Looking at this....weird
... ya. It looks like when they are hidden, the DOM still has the div with the margins set, but empty.
Were you able to find anything?
I'm still testing this out
Hmmm...I'm not able to recreate this. Here's with address:
And without
Here's my appearance object: appearance: {theme: 'night', labels: 'floating'}
Hey @desert grotto this thread is still open and I am on it though I misread Snufkin's update and thought we were waiting on you for new info. Let me catch up here for a minute
I had to step away before I read his last response. My apologies.
I am passing the following to the payment element on create. This hides the country and zip which is causing the spacing issues.
fields: { billingDetails: { name: 'never', email: 'never', address: 'never' } }
Is it just address that hides the country, or do all three need to be there?
Have you tried a page that is just this element and something under it? Is that the screenshot you already sent us?
I think just address. I have all three for the other services (Klarna, Clearpay, etc).
Yes, that's the screenshot I sent.
Here's what's under it.
Are those the only two things on that page? Because we couldn't reproduce, I am wondering how we can narrow down what might be causing that there
When you show Afterpay, there is no spacing when setting the billing details the same as above?
๐ I'm hopping in since @shadow jackal has to head out - give mea minute to catch up
OK, thank you.
I can confirm I'm seeing the same behavior when looking at the afterpay tab on payment element - let me see if there's any way to get rid of it
OK. Thanks.
I don't think there's any way to get rid of that extra spacing, but I can flag this as feedback to the team so they can fix it later