Actually the change event is now doing the correct thing, it should have the new value instead of the old version. We always had the problem that the App Connect state was a bit behind the actual DOM state, so it didn’t had the value directly since update was delayed for performance optimizations. Due to that problem we introduced the changed event that triggers after the App Connect was updated to have the updated value from the DOM.
With App Connect 2 we finally fixed the whole updating of the state, it is now directly and the DOM change event triggers after the value was updated.
I’ve now put in a small delay again for form elements to update its value to mimic the old App Connect behavior and for backward compatibility for users that depend on the old behavior.
Here the update: dmxAppConnect.zip (28.7 KB)