[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 bugzilla-daemon at webkit.org
Tue Feb 14 02:44:33 PST 2017


--- Comment #5 from Carsten Driesner <Carsten.driesner at open-xchange.com> ---
One of our web-based products (OX Documents) is highly dependent on key/composition events and is hurt by this wrong keypress event.

This website is a presentation of a colleague of me who explains how our product works using key-events.

If you or others want to try the product use "Try now" on https://www.open-xchange.com.

I am involved in browser-based composition for about two years now. I know more applications that are bound to correct key events in a contenteditable=true environment. E.g. look at this long running Chromium issue, where several people from different companies complained about wrong key codes (I think their applications could also see a negative impact by this issue) 

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/20170214/80533c29/attachment.html>

More information about the webkit-unassigned mailing list