#cberube_unexpected
random plankBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1225815338629730446
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
livid nestBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- cberube_error, 14 hours ago, 63 messages
tropic plover
No it is about LinkAuthenticationElement
olive bluff
Hi 👋 the LinkAuthenticationElement only collects an email address. I believe there is validation to help ensure a valid email format is provided. What validation beyond that were you expecting to see?
tropic plover
Input--invalid is not implemented and is overridden by p-Link. Looks like a bug to me as validation should be the same on all widgets.
Birder are not the same width as well
olive bluff
Sorry, I'm not following what you're describing.
Can you provide more details about your concern(s)?
olive bluff
Hi, do you have more details about the concerns you have about the styling? What would I need to do to reproduce the behavior you have concerns with?
tropic plover
Just compare validation from payment and LinkAuthenticationElement. The former does not have validation on it at all and when I hack it it is not similar.
olive bluff
I don't know what you mean by "compare validation", I'll try to ask more explicit questions to get an understanding of your concern. Sounds like you're working with our Appearance API and trying to use it to customize the Payment Element and Link Authenticaiton Element's appearances. Am I correct so far?
tropic plover
please check the picture. it is clear there is a validation quirk. The red box are different. More over, the link auhtentication does not follow the same validation pattern used for payment link.
olive bluff
When you say "validation quick" that's not what you mean, is it? You are more concerned about a UI difference, right?
Are you adjusting the styling of these elements at all? My test site is showing consistent styling for invalid values between the fields in my Payment Element and my Link Authentication Element.
tropic plover
No I dont. No do I provide any validators to the Link AUthentication elements.
tryied addding reuired to options but it doesn't seem to be supported.
This is what I do:
const linkAuthenticationElement = elements.create('linkAuthentication', {
defaultValues: {
email: customer?.email
}
});
olive bluff
Can you elaborate on what you mean you did by "tryied addding reuired", or what you were hoping to accomplish?
Do you have a publicly accessible test site showing this page?
olive bluff
How do I get to your test page from there?
olive bluff
I see the same styling for invalid values:
olive bluff
That link surfaces an error for me.
tropic plover
What browser Chroem and Edge do not work for me.
olive bluff
Chrome
tropic plover
I just realized Full name is part of addressElement.
I am trying to add validation like this:
fields: {
name: 'full',
phone: 'always'
},
validation: {
name: { required: 'full' },
phone: { required: 'always' }
}
olive bluff
That's not an option, only phone is supported in validation
https://docs.stripe.com/js/elements_object/create_address_element#address_element_create-options-validation
Similarly only phone is supported in fields
https://docs.stripe.com/js/elements_object/create_address_element#address_element_create-options-fields
livid nestBOT
tropic plover
Well.. not very interesting. we should be able to validate all fields.
olive bluff
Validations on name fields are really hard to do, it's hard to know what is considered a valid name everywhere.