[Webkit-unassigned] [Bug 202183] [Win] Update KeyboardEvent as per the latest specification
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Sep 30 01:01:24 PDT 2019
https://bugs.webkit.org/show_bug.cgi?id=202183
--- Comment #3 from Fujii Hironori <Hironori.Fujii at sony.com> ---
Firefox implementations looks quite complicated. I can't understand them.
Firefox also has the similer code to build a mapping table by using ToUnicodeEx in KeyboardLayout::LoadLayout.
But, I can't understand how this table is used.
It seems that Firefox is mapping a key code by using the following WM_CHAR events for printable keys,
and a hard-coded table for non-printable keys.
NativeKey::GetFollowingCharMessage retrieves queued WM_CHAR messages for printable keys.
KeyboardLayout::ConvertNativeKeyCodeToKeyNameIndex is converting non-printable keys.
https://dxr.mozilla.org/mozilla-central/source/widget/NativeKeyToDOMKeyName.h is the hard-coded table.
842927 - Implement DOM3 KeyboardEvent.key only for non-printable key, first
https://bugzilla.mozilla.org/show_bug.cgi?id=842927
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190930/caae10b0/attachment-0001.html>
More information about the webkit-unassigned
mailing list