Ole-Morten Duesund
a94a38071b
TagInput's onkeydown only commits on `e.key === 'Enter' || e.key === ','`. On Android Chrome with predictive text (GBoard et al), the soft keyboard keydown fires with `e.key === 'Unidentified'` and `e.keyCode === 229` during IME composition — the check misses entirely, the Enter never adds the tag, and the press instead bubbles up to the parent <form> and submits the whole activity. Result: impossible to tag from mobile. Fixes: - Track composition state via oncompositionstart / oncompositionend so we ignore commits while the IME is mid-composition. - Accept Enter via either `e.key === 'Enter'` OR `e.keyCode === 13` (and same for comma). preventDefault on every commit attempt so the parent form never submits accidentally. - Add an explicit "Legg til"-button next to the input. Foolproof mobile path — a tap is a tap, no IME involved. Desktop users still have Enter. - `enterkeyhint="done"` so the soft keyboard shows a sensible label on the action key. autocapitalize/autocorrect/spellcheck off so tags don't get mangled by autocomplete suggestions. Placeholder copy updated to mention the button. |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| index.html | ||
| svelte.config.js | ||
| tsconfig.json | ||
| vite.config.ts | ||