Hi @patrick, I found another one, unfortunately.
The autocomplete component’s on changed is not fired (updated works). I’m on today’s release.
Let me know if you need more info.
Thanks!
Hi @patrick, I found another one, unfortunately.
The autocomplete component’s on changed is not fired (updated works). I’m on today’s release.
Let me know if you need more info.
Thanks!
Added the event, here an update for testing
dmxAutocomplete.zip (7.7 KB)
Thank you @patrick! Almost there, it seems that changed and updated are fired at same time.
So I get both updated and changed events when I give a new input as an user (that is good)
But also when I update the value with .setValue() (not ideal)
The only time updated is fired alone is on pageload - But then it fires twice. (I don’t mind this, just extra info that might help)
Let me know if you need more info!
Thank you for the feedback. Please let me know if the following update improves it.
dmxAutocomplete.zip (7.7 KB)
Thank you so much, it’s working!
(Just FYI, the updated even still fires twice on pageload, but that is not a problem for me, just to make sure I give the complete picture)
It probably triggers twice since your data source for the autocomplete needs some more time and the value gets updated after the data was loaded. Will leave it like this.
Fixed in Wappler 6.5.0
This topic was automatically closed after 29 hours. New replies are no longer allowed.