<div class="gmail_quote">On Thu, Jul 29, 2010 at 9:18 AM, Joone Hur <span dir="ltr"><<a href="mailto:joone@kldp.org">joone@kldp.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Jul 29, 2010 at 3:13 AM, Oliver Hunt <<a href="mailto:oliver@apple.com">oliver@apple.com</a>> wrote:<br>> On Jul 28, 2010, at 8:45 AM, Joone Hur wrote:<br>>> 3) Keyboard events should not be dispatched during a composition.</div>
<div class="im">
> Key events must be sent while an IME is active otherwise sites break. IIRC you get keydown and keyup events, but not keypress. The keydown event when an IME is active has charCode 229 in order to be compatible with IE.</div>
</blockquote><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
</div>However, I think<br>
that composition events seem enough without keyboard events during a<br>
IME composition.</blockquote><div><br></div><div>If were were designing these APIs from scratch, that might be the case. But WebKit only recently added composition events. We have been firing key events for a long time. If we stopped firing them, a lot of sites would break in WebKit browsers. So, not firing them is not an option.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We need a consensus on this issue between WebKit and Mozilla developers.<br></blockquote><div><br></div><div>
I don't think we could reasonably stop firing key events. Too many sites would break.</div><div><br></div><div>Ojan</div></div>