incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bowser (JIRA)" <>
Subject [jira] [Resolved] (CB-265) IFrame loaded from jQuery in the navigation history
Date Thu, 10 May 2012 18:54:47 GMT


Joe Bowser resolved CB-265.

    Resolution: Fixed

Actually, I ran the native tests, and this now works correctly for our demo.  I'm going to
assume it works when jQuery changes the src attribute as well.  Going to close this one since
CB-585 fixes it if you use the browser history.
> IFrame loaded from jQuery in the navigation history
> ---------------------------------------------------
>                 Key: CB-265
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.3.0
>         Environment: The wrong behavior was observed on an Asus Transformer TF101 tablet,
with Android 3.2.1.
> The behavior could not be reproduced on a Samsung Galaxy S (GT-I9000), with Android 2.3.4.
>            Reporter: Adrián Chaves Fernández
>            Assignee: Joe Bowser
>              Labels: android, history, iframe, jquery
>             Fix For: 1.8.0
> Using jQuery Mobile, an application with two pages. On the second page there is an IFrame
element with no source (src=""). jQuery Mobile's OnPageBeforeShow event is used to set the
src property to a website (tested with OSM and like this:
> jQuery('#IFrame').attr('src', '');
> The page is successfully loaded inside the iframe.
> When you go back then, either with the Back button of the Android device or with the method, the content of the IFrame dissapears. If you hit Back
again (any of the methods also), then it works as expected.
> Seems the load of the iframe is counted as a third page on the application.
> The thing is, on the mobile device I used it works as expected (as I expect at least),
hitting back takes you to the previous page directly.

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