incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <>
Subject [jira] [Commented] (CB-1184) Phonegap crashes on ios status bar tab when using page change transition effects
Date Thu, 02 Aug 2012 22:59:02 GMT


Shazron Abdullah commented on CB-1184:

Regarding the Stack Overflow issue - we use the iframe because it fixes critical issues in
WebKit, e.g. when you set innerHTML on an element, it will not render the contents. Using
document.location screws this up somehow in the current frame. A lot of JavaScript frameworks
use this functionality, and this was breaking it - thus we can't revert.
> Phonegap crashes on ios status bar tab when using page change transition effects
> --------------------------------------------------------------------------------
>                 Key: CB-1184
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: iOS
>    Affects Versions: 1.9.0, 2.0.0
>            Reporter: Andrew Kirkovski
>            Assignee: Shazron Abdullah
>         Attachments: crash1.log, crash2.log
> This is not 100% reproducable, but seems to be a known problem:
since 1.4 Phonegap
> I wonder why it is not yet fixed.
> I use translate3d to make ios use hardware acceleration and make transitions smooth.
But that leads to status bar taps crashes app. When not using page transition effects, app
works just fine.
> Possible steps to reproduce.
> 1. Load 2 heavy divs with graphics, divs styled as -webkit-overflow-scrolling: touch;
> If divs are not heavy enough, bug is too unreproducable. 
> 2. Children of divs styled as -webkit-transform: translateZ(0) to prevent them from disappearing
during scroll
> 3. apply a transition to divs with hardware acceleration and transition. Like from "translateZ(0)
scale(0,0)" to "translateZ(0) scale(1,1)"
> 4. tab status bar. App crashes

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