Closed Bug 1477639 Opened 6 years ago Closed 6 years ago

keyup event is not fired at first for Korean input

Categories

(Core :: DOM: Events, defect)

61 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 354358

People

(Reporter: cs09gi, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID: 20180704003137

Steps to reproduce:

I'm trying to make auto-fill search input. set keyup event to trigger auto-fill function, typed Korean character(ㄱ,ㄴ,ㄷ,...), keyup event was not fired.(it works when you copy but type)


Actual results:

when the input is Korean character, it's not fired until any alphabet typed or arrow button on keyboard pressed.


Expected results:

keyup event should be fired for Korean input as Alphabet.
Component: Untriaged → Widget: Win32
Product: Firefox → Core
This is long standing bug and will be fixed on Beta and Release channels in the near future, but not yet fixed the schedule (already fixed on Nightly).

On the other hand, using keydown/keyup event for detecting text input is wrong approach. keydown and keyup are just physical key state event. So, if user inputs text without keyboard such as handwriting input or voice input, those events may not be fired anyway (depends on how OS treat such input).

So, you should use "input" event instead. You can check if input event occurs during composition with InputEvent.isComposing even without "compositionstart" and "compositionend".
https://w3c.github.io/uievents/#event-type-input
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Component: Widget: Win32 → DOM: Events
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.