Skip to content

Commit 1989bf3

Browse files
authored
Clarify IME caveat tip (#804)
Previously, the tip on using `input` to listen to IME-based composition input was unclear. In the context of the preceding statement about `textarea` and `input type=text` elements using `input`, it seemed that composition with v-model should work with those inputs. This change makes it clear that `v-model` should be replaced with a custom `@input/:value` pair.
1 parent 1cd0184 commit 1989bf3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/guide/forms.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ You can use the `v-model` directive to create two-way data bindings on form inpu
1616

1717
<span id="vmodel-ime-tip"></span>
1818
::: tip Note
19-
For languages that require an [IME](https://en.wikipedia.org/wiki/Input_method) (Chinese, Japanese, Korean etc.), you'll notice that `v-model` doesn't get updated during IME composition. If you want to cater for these updates as well, use `input` event instead.
19+
For languages that require an [IME](https://en.wikipedia.org/wiki/Input_method) (Chinese, Japanese, Korean etc.), you'll notice that `v-model` doesn't get updated during IME composition. If you want to respond to these updates as well, use an `input` event listener and `value` binding instead of using `v-model`.
2020
:::
2121

2222
### Text

0 commit comments

Comments
 (0)