Update a text input problems about elm-form HOT 7 CLOSED

Yes, this solution is for the UI, e.g.:

Input.textInput state
             [ class "form-control"
             , value (Maybe.withDefault "" state.value)
             ]

This should solve the UI not reflecting the state. The note on Initial values and reset on the doc have more information.

from elm-form.

Hi! I think your problem is related to this issue: #54

Try setting the value attribute of the input to reflect the value of the input stored in the model.

Let me know if it works :)

from elm-form.

I'm so glad I'm not alone!

Note that I an using a Text Input, not a text area.

The value is updating correctly I think. If you look at the video it ends at "Customer 2" but that is not reflected in the UI

from elm-form.

Thanks - that worked. Now I just have to see what 'types too fast means'!

from elm-form.

Maybe it's related to how good your hardware is, but you can try this to reproduce the bug:

1. Type something in the input (e.g: pablohirafuji| <-- caret representation)
2. Move the caret to the start of your typed text in the input (e.g: |pablohirafuji)
3. Bash at the keyboard with all your fingers until the caret go to the end of the input (should see something like this: ljkgsefjlkgsdfpablohirafujilkjashljkhdf|)

Please note that this bug only occurs when using the value attribute to reflect the model's value. By default, the package use defaultValue. The defaultValue attribute only work on unmodified inputs. That's why when you make any change to the input's value, it no longer reflect the model's value, but still sends the input's value to the update function using the oninput event.

from elm-form.

It feels unexpected that only defaultValue is updated when calling Input.textInput. Anyhow, thanks @pablohirafuji for pointing out the solution and referencing the docs.

from elm-form.

@alexmunda Yeah, I also thought so. But setting the value attribute has hard side effect on Test frameworks, while defaultValue has practically no side effect. The user can always set the value, but not unset.

Just to make it clear to anyone who read this issue, the "type too fast" bug is not related to the package, it's an Elm/Virtual Dom issue. Last time I checked, React has a workaround doing something like this:

• If the input is focused, unset the value attribute, otherwise, set the value attribute

Witch brings other issues, but all managed internally.

from elm-form.