From 2a2592272ccaae87abc631eaa0f2434d4b483440 Mon Sep 17 00:00:00 2001 From: Tyler Mercer <40773575+tylermercer@users.noreply.github.com> Date: Tue, 12 Jan 2021 12:49:21 -0700 Subject: [PATCH] Clarify IME caveat tip 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. --- src/guide/forms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/forms.md b/src/guide/forms.md index 6b2c7a53e1..7eabf9826f 100644 --- a/src/guide/forms.md +++ b/src/guide/forms.md @@ -16,7 +16,7 @@ You can use the `v-model` directive to create two-way data bindings on form inpu ::: tip Note -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. +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`. ::: ### Text