[Webkit-unassigned] [Bug 167880] WebKit provides a keypress event with wrong which/keyCode/charCode directly after a composition started with ^, =?UTF-8?Q?=C2=B4?=, ` completes

[bugzilla-daemon at webkit.org]

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

--- Comment #2 from Carsten Driesner <Carsten.driesner at open-xchange.com> ---
I think there is no single correct solution for this scenario. Chrome and Firefox use different events to report what happens, but the events are consistent.

E.g. Chrome 56.0.2924.87 on Mac reports the following events (this time order is top to bottom)

- keydown 229
- compositionstart
- dom actually changed
- DOMCharacterDataModified
- DMSubtreeModified
- input
- keyup 187
- keydown 229
- textInput
- dom actually changed
- DOMCharacterDataModified
- DOMSubtreeModified
- dom actually changed
- DOMCharacterDataModified
- input
- compositionend, data=´v
- keyup 86

Both entered keys are notified by the "compositionend" event.

For your second  
The '´' character is reported by the "compositionend" event (which is correct as '´' starts a composition) and the following 'v' key by "keydown/keypress/keyup" events. Therefore there should be theoretical no problem to fix this issue, the values of which, charCode, keyCode must be in that case 118 (corresponding to the second key v). I am sure that internally this is less easy and there is a bunch of problems regarding state and so on.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170209/104f68c1/attachment-0001.html>