Wappler Version : 4.7.3
Operating System : W11
Server Model: NodeJS
Database Type: MySQL
Hosting Type: Custom
Expected behavior
Setting the value of a tagify text box when the page loads should not trigger the add/remove events.
Actual behavior
When setting the value (where the data is fetched from a server connect action) of a tagify text input through the value dynamic attribute, it fires the “Add” and “Remove” dynamic events. As such, whenever you load a page these actions are instantly triggered making them completely unusable if you are setting the value from a server connect.
I am assuming this is not intentional because it doesn’t happen with the Wappler “changed” event, but of course, you can’t use the tagify events on that.
I haven’t tested setting the value through other methods, but I assume this also triggers the events. Essentially, they should not be triggered when app connect sets the value initially, just like the changed event.
How to reproduce
- Create a tagify text input.
- Add the “Value” dynamic attribute and set the value to be data from a server connect.
- Add the “Add” and/or “Remove” events and make them trigger an alert (as an example).
- Load the page. The add/remove events will be triggered instantly without user input as Wappler sets the value.
Last updated: