@tony.kay So it is indeed because of a mismatch in the value property that you implemented wrap-form-element?

It;s just how the form components work in React…they are designed to be controlled with component-local state only, so you kind of have to hack them to control them async

not sure what your comment means “mismatch in the value”

the trick is to pre-change the input (via CL state) so that when the async change comes it already matches what you ahve and prevents the cursor jump