#rodneyrenolds_unexpected
valid wrenBOT
đ 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/1360304407215997020
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- rodneyrenolds_unexpected, 1 day ago, 14 messages
- rodneyrenolds_code, 2 days ago, 18 messages
feral parcel
Hi, typically that means you're calling something else or another Promise or callback in between the raw .on('click)' event and where you call elements.submit()
It has to be completely simple, button click event -> call back -> elements.submit(), if you add anything else it won't work.
Can you debug your page from this angle?
stuck blade
Ah, that's probably what it is then. We're updating a lot of data via a REST call to our API before submitting the payment
I'm not sure how we're going to be able to get around that though
feral parcel
That is up to you, but you'd just want to ensure that it is simple between the click event and submit.
stuck blade
I'll have to take this back to the team. Thanks for the insights!