#gpbl_cardelement-voiceover
1 messages ยท Page 1 of 1 (latest)
๐ 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/1229474913828732938
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi ๐
What element are you creating?
Hi there! Im a creating cardNumber, cardCVC and cardExpiry elements. All expose the same behavior...
Notably on Chrome/MacOS, they render as type="text" so i assume this is a Safari-only behavior, maybe to show the proper keyboard to iOS users?
Okay I haven't been able to replicate this in Chrome.
so this occurs only with Safari?
Right! indeed it happens only in Safari.
Okay I can repro
Unfortunately this isn't something you or I can change
I will have to raise this internally
Oh I could imagine that! It would be great if we could get some help to fix this.
is there some support ticket we can open with Stripe ? WCAG compliance is a legal requirement for our web app.
I will raise this internally. If you want to be kept updated with progress for this you can write in to Support
https://support.stripe.com/contact
It will be very important you are extremely crips and clear in your request. Be sure to include some examples of the <input> elements in both Chrome and Safari.
These details act as a signal to get your request routed to the right team
Hey thanks so much for the help and the tips ! Will write my request there. Glad you could reproduce it !!
Alright, I have raised this issue. I hope we are able to resolve it quickly for you