yeuimu
6c61a4e871
- Debian-based api image (bookworm-slim), docker/debian mirrors, prisma binaryTargets for openssl 3.0 - nginx: admin SPA under /admin, TLS via acme.sh (ZeroSSL) + auto-renewal cron, http->https redirect - prisma: add origin_goods.delisted migration, sync missing schema (good_image/tag_font_color/good_tags), fix users.createdAt Timestamptz - api: CORS wildcard reflection, helmet CORP cross-origin, price backfill in persistProductDetail, categoryIcon ancestor fallback, mediaByColor per-color gallery in public goods detail - admin: /admin base path (vite + router) - import-data.mjs: udt_name casting, serial sequence advance fix
2.9 KiB
2.9 KiB
title, impact, impactDescription, type, tags
| title | impact | impactDescription | type | tags | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| v-model Does Not Update During IME Composition | MEDIUM | v-model won't capture intermediate input for Chinese, Japanese, Korean and other IME languages | capability |
|
v-model Does Not Update During IME Composition
Impact: MEDIUM - When users type in languages that require an Input Method Editor (Chinese, Japanese, Korean, etc.), v-model won't update until the composition is complete. This breaks real-time validation, character counters, and live search features for international users.
IME (Input Method Editor) allows users to compose complex characters by typing multiple keystrokes. During this composition phase, v-model deliberately waits until the user confirms their selection before updating. This is usually desired, but can break features that need every keystroke.
Task Checklist
- Test forms with IME input if your app serves CJK (Chinese, Japanese, Korean) users
- For real-time features (live search, character counters), use manual event binding instead of v-model
- Consider both behaviors when designing - sometimes waiting for composition completion IS correct
- Document expected behavior for international users
Problem - v-model waits for composition:
<script setup>
import { ref } from 'vue'
const searchQuery = ref('')
const charCount = ref(0)
</script>
<template>
<!-- PROBLEM: During IME composition, searchQuery won't update -->
<!-- Chinese user types "ni hao" -> sees no results until they press space/enter -->
<input v-model="searchQuery" placeholder="Live search...">
<p>{{ searchQuery.length }} characters</p>
<!-- Character counter stays at 0 during IME input -->
</template>
Solution - Manual event binding for real-time updates:
<script setup>
import { ref } from 'vue'
const searchQuery = ref('')
// This captures EVERY input event, including during IME composition
function handleInput(event) {
searchQuery.value = event.target.value
}
</script>
<template>
<!-- CORRECT: Manual binding captures all input, including IME composition -->
<input
:value="searchQuery"
@input="handleInput"
placeholder="Live search..."
>
<p>{{ searchQuery.length }} characters</p>
</template>
<!-- Shorter inline version -->
<input
:value="searchQuery"
@input="event => searchQuery = event.target.value"
>
When v-model behavior IS correct:
<!-- For form submission, waiting for composition IS usually better -->
<!-- User expects to confirm their character selection before it's "official" -->
<input v-model="formName" placeholder="Enter your name">
<!-- The final composed characters will be submitted, not intermediate states -->