You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presumably the issue is that this is invalid html (I inadvertently kept the type_ attribute from when the textarea was an input element before), so I'm not sure whether it's beyond the scope of the package to prevent against this type of invalid HTML issue.
The text was updated successfully, but these errors were encountered:
I assume you already saw the docs for type_. I agree that this probably warrants a rework of the API considering it can result in a runtime error, which is one of the main things Elm tries to prevent. I'm just not entirely sure how to do so within Elm's type system.
Here are two variations of the same bug:
SSCCEs:
Trying to render the invalid DOM element initially (TypeError: Attempted to assign to readonly property outputted once)
When the DOM is patched after a successful render (Click edit button: TypeError: Attempted to assign to readonly property, outputted repeatedly.)
Presumably the issue is that this is invalid html (I inadvertently kept the type_ attribute from when the
textarea
was aninput
element before), so I'm not sure whether it's beyond the scope of the package to prevent against this type of invalid HTML issue.The text was updated successfully, but these errors were encountered: