[Webkit-unassigned] [Bug 204694] New: [Win] Retrieve all following WM_CHAR events at the beginning of processing WM_KEYDOWN event

[bugzilla-daemon at webkit.org]

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

            Bug ID: 204694
           Summary: [Win] Retrieve all following WM_CHAR events at the
                    beginning of processing WM_KEYDOWN event
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: Hironori.Fujii at sony.com

[Win] Retrieve all following WM_CHAR events at the beginning of processing WM_KEYDOWN event

In Windows ports, WM_KEYDOWN dispatches keydown event, and
WM_CHAR dispatches keypress event. If a keydown event is canceled
by calling preventDefault, the following corresponding keypress
events shouldn't be dispatched.

WebKit1 implements it by removing WM_CHAR events if the keydown
event is consumed. However, WebKit2 can't do so because WebKit2
processes key events asynchronously. Thus, retrieve all following
WM_CHAR events, and dispatch them after processing the keydown
and it is not consumed.

In addition to that, retrieving following WM_CHAR events are
needed to fix Bug 204672 because the events are needed for 'key'
property of keydown KeyboardEvent for dead key combination.

Gecko and Chromium also implements 'key' property in the same approach.

Bug 204672 – [Win] 'key' property of keydown KeyboardEvent doesn't have the diacritic for alphabet key following a dead key
Bug 200558 – [Win][WebKit2] Can't prevent input events by canceling keydown events

-- 
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/20191129/14c1382f/attachment.htm>