-
Notifications
You must be signed in to change notification settings - Fork 34
Update a text input problems #65
Comments
Hi! I think your problem is related to this issue: #54 Try setting the Let me know if it works :) |
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 |
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. |
Thanks - that worked. Now I just have to see what 'types too fast means'! |
Maybe it's related to how good your hardware is, but you can try this to reproduce the bug:
Please note that this bug only occurs when using the |
It feels unexpected that only defaultValue is updated when calling |
@alexmunda Yeah, I also thought so. But setting the 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:
Witch brings other issues, but all managed internally. |
Hi, I will try to work on an example, but wanted to flag a problem straight away. I have a text input that filters the possible choices as you type. When you click on a choice it updates the text input.
That works, but if you then start deleting the input text, such that more choices appear again, then clicking a second time on the list does not update the text input any more.
Video at: https://youtu.be/L8DbIBFF5_U?rel=0
Note how at the end the input value is "Customer 2", but you do not see that in the input box.
If you have any ideas, I would welcome it. (I'm certainly not convinced that the problem lies with elm-form, but I do something similar on a simpler form elsewhere in my site without elm-form, and then I don't have the same issues)
The text was updated successfully, but these errors were encountered: