Return-Path: 
 <callback-dev-return-11164-apmail-incubator-callback-dev-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 08B8B91BC
	for <apmail-incubator-callback-dev-archive@minotaur.apache.org>;
 Thu,  2 Aug 2012 19:54:03 +0000 (UTC)
Received: (qmail 91587 invoked by uid 500); 2 Aug 2012 19:54:02 -0000
Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org
Received: (qmail 91560 invoked by uid 500); 2 Aug 2012 19:54:02 -0000
Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:callback-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:callback-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:callback-dev@incubator.apache.org>
List-Id: <callback-dev.incubator.apache.org>
Reply-To: callback-dev@incubator.apache.org
Delivered-To: mailing list callback-dev@incubator.apache.org
Received: (qmail 91550 invoked by uid 99); 2 Aug 2012 19:54:02 -0000
Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Aug 2012 19:54:02 +0000
Received: from isssues-vm.apache.org (localhost [127.0.0.1])
	by issues-vm (Postfix) with ESMTP id 8E52814052C
	for <callback-dev@incubator.apache.org>;
 Thu,  2 Aug 2012 19:54:02 +0000 (UTC)
Date: Thu, 2 Aug 2012 19:54:02 +0000 (UTC)
From: "Joe Bowser (JIRA)" <jira@apache.org>
To: callback-dev@incubator.apache.org
Message-ID: <929905200.6975.1343937242586.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <776494391.6771.1343931364579.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Resolved] (CB-1181) onkeyup not firing in javascript on
 Jellybean
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/CB-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe Bowser resolved CB-1181.
----------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0

The super.onKeyUp must be called on JB, because the WebView is modifying this onKeyUp.  Google has made their WebView far more brittle by doing this, sadly.
                
> onkeyup not firing in javascript on Jellybean
> ---------------------------------------------
>
>                 Key: CB-1181
>                 URL: https://issues.apache.org/jira/browse/CB-1181
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android, CordovaJS
>    Affects Versions: 2.0.0
>         Environment: Android 4.1.1 (Nexus 7), versus 4.0.4 (Samsung Galaxy Tab 2 10")
>            Reporter: Ken Corey
>            Assignee: Joe Bowser
>             Fix For: 2.1.0
>
>
> I've got a dynamic search entry something like this in my index.html:
> -------------------------------------------------------------------
> <script>
> function dosearch(txt) {
>   // blah
>   console.log("IAmSearching is true.");
>   // lots of stuff
>   console.log("IAmSearching is false.");
> }
> </script>
> <input id="junk" onkeyup="dosearch(this.value);">
> ------------------------------------------------------------------- 
> On a Nexus 7 (Jelly Bean 4.1.1), dosearch is only being called when I press <return> with the input active.
> Now, on 4.0.4 (Samsung Galaxy Tab 2 10), dosearch is being called for every keystroke, as intended.
> Note that in the logcats, on Samsung, the webview itself seems to be handling the onkeyup without cordova getting a look in. On the Nexus, it's the opposite.
> Here's a comparison of the relevant bit of the logcats:
> http://pastebin.com/TvgQESb1 
> Can anyone tell me why Cordova 2.0 has a problem with keyup events on 4.1.1?
> Feel free to contact me (ken@kencorey.com) if you need confirmation or better logging.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira