#victor_elements-no-change-event
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/1354455943047549048
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there π I am seeing something similar on my test site, and am a bit surprised by it as well.
I'm looking to see if maybe we only emit the events when the complete value swaps from true to false, or if the customer provides potentially valid details for the other fields rather than on every keystroke.
Hm, yeah, this isn't how I thought this behaved. I'm going to have to do some digging.
I'm trying to check in with the product team that owns this behavior to confirm whether this is expected.
Hi π
I wanted to follow up and say that our product team is looking into this but it will take longer than we can leave this thread open for. I will be sharing a link with you to create a support ticket that will get routed directly to us so we can provide you with updates as we receive them.
Hello @frozen iris, we have sent you a direct message, please check it at https://discord.com/channels/@me/1354493029628772563
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.