Closed srid closed 1 year ago
This is quite common. In fact, even adding
textAreaElement $ def & textAreaElementConfig_initialValue .~ "some value"
to the project generated by ob init
will reproduce this error.
It could be related to the fact, that this code uses TextArea.setValue
which was auto-generated and looks fishy because textarea
actually has no value attribute. But then the setValue
functionality of reflex-dom textareas works as expected and also uses TextArea.setValue
..
This is quite possibly fixed by https://github.com/reflex-frp/reflex-dom/pull/400
@tomsmalley That seems like it should fix the issue. TextArea.setValue
doesn't seem to be the culprit since it sets the value by javascript internally and that is possible.
Here's the code that defines the textarea element:
https://github.com/srid/MarkdownPreview/blob/89ec7c2fb2206f01219709f86c29fd53f12e8218/frontend/src/Frontend.hs#L34-L38
To reproduce, clone this repo (at commit
89ec7c2
if it matters), and runob run
. You will notice that the app loads with an empty textbox, instead of being initialized withHello *world*
.