incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Created] (CB-865) Reopening app after calling exitApp() does not render HTML page completely
Date Tue, 05 Jun 2012 17:12:23 GMT
Filip Maj created CB-865:

             Summary: Reopening app after calling exitApp() does not render HTML page completely
                 Key: CB-865
             Project: Apache Cordova
          Issue Type: Bug
          Components: Android
    Affects Versions: 1.6.0, 1.5.0, 1.4.0, 1.3.0
         Environment: Apparently can be reproduced on Android 2.3 Emulator with PhoneGap 1.6.
Physical devices: Samsung galaxy SII, Nexus S. 
            Reporter: Filip Maj
            Assignee: Joe Bowser
            Priority: Minor

Needs verification.

>From google groups:

Other pertinent info:

I'm facing a weird bug : i've bound the physical return button to in order to exit the app. 
It works fine, but when i'm returning in the app, the display is not fully 
displayed, the app seems to works fine, but only 2/3 of the page is 
displayed, the other 1/3 displays only the background color. 


I noticed that this space is not always the same, i can navigate to other 
page of my app and some have a bigger space (equivalent to the keyboard), 
some pages are totally fine (no space at all), and some have a smaller 
space than the keyboard. And some page doesn't work at all. I use JQTouch 
if it can helps. 
It's really weird. I checked the adb log i'm not finding anything usefull. 
This is the same behaviour in the emulator and in my two devices. 

Wow, that's weird. When i attach weinre the bug disappear, the app works like a charm. I can
resume it and come back without any problem.... 

My app use only portrait mode 

Actually, putting a <script src="thisdoesntexist.js"></script> cause the 
app block a little bit the loading, and resolve the problem... 

And if i put this hack on the bottom of the page, it doesn't make the app 
slower, and it resolve the problem.. 
But still want to find a better workaround ;-) 

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