The reason we switched to keyUp is so you could slide your finger off the up button in case you changed your mind about clicking on the back button.
I noticed that you checked in: https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-android.git;a=commit;h=180696baec28d6e6b67e8bb23a5302f21bce6b79 On my Samsung Galaxy Note running Android 2.3.6 the back button does not work. That is when I do not regisiter for a "backbutton" listener and I expect that when I click the back key that my app would exit. With our fix the back button doesn't exit the app. I have to click the home button to exit. Reverting your change returns the back button behaviour to normal. So something is still janky. I haven't been able to test it on my phone as I can't convince it to be recognized on my laptop. Simon Mac Donald http://hi.im/simonmacdonald On Tue, Apr 17, 2012 at 8:46 PM, Joe Bowser <[email protected]> wrote: > Hey > > Remember this issue: > https://issues.apache.org/jira/browse/CB-367 > > I'm surprised that I'm catching it now, but the Back Button is really janky > on my Nexus S running 2.3.6, and I'm working on a fix now. What was the > reasoning behind the Back Button being on the keyUp instead of the keyDown? > I don't remember. > > Joe >
