[Android] Change "handling" of unhandled key events.

[Android] Change "handling" of unhandled key events.
    
    When we receive an IME Key Down event in Android, we forward it to
    WebKit for processing as RawKeyDown, followed by a WebInputEvent::Char
    if it had a character associated with it.
    
    When typing into a text field or textarea, if the RawKeyDown  triggers
    an editing event it will go unhandled by WebKit, and it's the subsequent
    Char event that WebKit handles. The unhandled RawKeyDown is propogated
    back down to the Browser and out to the embedder. In the Android WebView
    where we then propogate the unhandled event to the WebView embedder.
    
    However - as the Char event is going to be handled by the textarea
    later, informing the embedder that the KeyDown wasn't handled isn't
    what it expects and we shouldn't do so. We should only propogate an
    unhandled Char event to the WebView embedder.
    
    This CL fixes this by using the NativeWebKeyboardEvent.skip_in_browser
    flag to prevent browser side handling of the RawKeyDown. It also
    fixes a bug in the propogation of the synthetic Char event.

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=208659

[aurimas (slooooooooow), 2013-06-21 17:01:45]

+yusufo who worked on key event handling.

[Yusuf, 2013-06-24 23:26:56]

On 2013/06/21 17:01:45, aurimas wrote:
> +yusufo who worked on key event handling.

lgtm

[benm (inactive), 2013-06-25 00:31:11]

+sievers for OWNERS

[no sievers, 2013-06-25 19:16:05]

lgtm

[commit-bot: I haz the power, 2013-06-26 04:56:11]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/benm@chromium.org/17074005/4001

[commit-bot: I haz the power, 2013-06-26 06:36:36]

Change committed as 208659