mirrors/leptos-book
1
0
Fork 0
mirror of https://github.com/leptos-rs/book.git synced 2025-12-27 10:01:41 -05:00
Code Issues Packages Projects Releases Wiki Activity

update <textarea> comment for 0.7

Browse Source
This commit is contained in:
Greg Johnston
2025-05-02 15:25:30 -04:00
committed by GitHub
parent 1f603bbf3b
commit b4a1975f83
1 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/view/05_forms.md
View File

@@ -210,16 +210,12 @@ Two form elements tend to cause some confusion, in different ways.
### `<textarea>`
Unlike `<input>`, the `<textarea>` element does not support a `value` attribute.
Instead, it receives its value as a plain text node in its HTML children.
Unlike `<input>`, the `<textarea>` element does not support a `value` attribute in HTML.
Instead, it receives its initial value as a plain text node in its HTML children.
In the current version of Leptos (in fact in Leptos 0.1-0.6), creating a dynamic child
inserts a comment marker node. This can cause incorrect `<textarea>` rendering (and issues
during hydration) if you try to use it to show dynamic content.
Instead, you can pass a non-reactive initial value as a child, and use `prop:value` to
set its current value. (`<textarea>` doesn’t support the `value` **attribute**, but _does_
support the `value` **property**...)
So if you’d like to server render an initial value, and have the value also react in the browser,
you can both pass it an initial text node as a child and use `prop:value` to
set its current value.
```rust
view! {
@@ -227,8 +223,7 @@ view! {
prop:value=move || some_value.get()
on:input:target=move |ev| some_value.set(ev.target().value())
>
/* plain-text initial value, does not change if the signal changes */
{some_value.get_untracked()}
{some_value}
</textarea>
}
```