<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WebKit provides a keypress event with wrong which/keyCode/charCode directly after a composition started with ^,´,` completes"
href="https://bugs.webkit.org/show_bug.cgi?id=167880#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WebKit provides a keypress event with wrong which/keyCode/charCode directly after a composition started with ^,´,` completes"
href="https://bugs.webkit.org/show_bug.cgi?id=167880">bug 167880</a>
from <span class="vcard"><a class="email" href="mailto:Carsten.driesner@open-xchange.com" title="Carsten Driesner <Carsten.driesner@open-xchange.com>"> <span class="fn">Carsten Driesner</span></a>
</span></b>
<pre>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.
<a href="http://www.slideshare.net/Malte.Timmermann/ox-documents-explained">http://www.slideshare.net/Malte.Timmermann/ox-documents-explained</a>
If you or others want to try the product use "Try now" on <a href="https://www.open-xchange.com">https://www.open-xchange.com</a>.
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)
<a href="https://bugs.chromium.org/p/chromium/issues/detail?id=118639">https://bugs.chromium.org/p/chromium/issues/detail?id=118639</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>