[Webkit-unassigned] [Bug 202183] [Win] Update KeyboardEvent as per the latest specification

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=202183

--- Comment #4 from Fujii Hironori <Hironori.Fujii at sony.com> ---
I think this problem can be solved more simply.
The problem is:
- TranslateMessage is using ToUnicodeEx
- ToUnicodeEx stores a previous dead key
- extra calling ToUnicodeEx consumes the stored dead key

For example, typing '`' and 'a':

- Types '`'
- The first calling ToUnicodeEx from TranslateMessage stores '`' as a dead key
- Types 'a'
- The second calling ToUnicodeEx from TranslateMessage returns 'à' as expected

The problem happens if ToUnicodeEx is used after calling TranslateMessage

- Types '`'
- The first calling ToUnicodeEx from TranslateMessage stores '`' as a dead key
- Extra calling ToUnicodeEx with '`' consumes the stored dead key, and return '``'
- Types 'a'
- The second calling ToUnicodeEx from TranslateMessage unexpectedly returns 'a'

This problem can be solved by one more extra calling ToUnicodeEx with VK_SPACE.

- Types '`'
- The first calling ToUnicodeEx from TranslateMessage stores '`' as a dead key
- ToUnicodeEx(VK_SPACE) consums the dead key
- ToUnicodeEx('`') stores a dead key again
- Types 'a'
- The second calling ToUnicodeEx from TranslateMessage returns 'à' as expected

https://en.wikipedia.org/wiki/Dead_key

-- 
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/20191008/261ac35a/attachment.html>