incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon MacDonald (Commented) (JIRA)" <>
Subject [jira] [Commented] (CB-283) Disabling the back button handler doesn't give control back to the main Activity
Date Tue, 28 Feb 2012 20:21:46 GMT


Simon MacDonald commented on CB-283:

Well I was looking into this but it looks like Joe is all over it and I have to go pick up
my daughter anyway. From what I've been able to tell when you call:

    document.removeEventListener('backbutton', interceptBackbutton, false);

The code event listener is being removed from the list of registered events but the code to

      onUnsubscribe:function() {
        // If we just detached the last handler, let native know we no longer override the
back button.
        if (this.handlers.length === 0) {
          exec(null, null, "App", "overrideBackbutton", [false]);

for backbutton is never called.
> Disabling the back button handler doesn't give control back to the main Activity
> --------------------------------------------------------------------------------
>                 Key: CB-283
>                 URL:
>             Project: Apache Callback
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: Master
>            Reporter: Simon MacDonald
>            Assignee: Filip Maj
>            Priority: Blocker
>             Fix For: 1.5.0
> Go into the mobile spec tests, tap "Events", tap "Intercept backbutton", click the hardware
back button. You should see an line printed in the results section "Back button intercepted".
Now tap "Stop intercept of backbutton" and then click the hardware back button. You'll notice
the app does not go back to the previous page. 
> Looking at the logs you will see:
> I/InputDispatcher(  129): Delivering key to current input target: action: 1, channel
'40c840b0 com.phonegap.mobilespec/com.phonegap.mobilespec.MobileSpec (server)'

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message