Home/ Questions/Q 7172383
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T15:36:16+00:00

I am having a problem with an application I am writing in jquery mobile

  • 0

I am having a problem with an application I am writing in jquery mobile and phonegap. While testing in the browser, I had no problems using the back button (no phonegap js involved). However once I try on a device with the phonegap js it breaks.

Steps to reproduce:

  1. Load app
  2. Visit several pages (linked internally using #)
  3. Click the back button or call history.back() from anywhere (using the js console, or by triggering something that calls it)

On the browser (chromium, firefox etc), it goes back one ‘page’ (to the previous # link whatever it was). This is the preferred behaviour.

On the device (iPhone 4, iPhone simulator, Android 2.2 (device), Android 3.2 (device)), it goes to the first/landing page (the first ‘page’ in the index.html file).

I suspect that the problem is with phonegap. Is there a way to revert to the preferred behaviour or the browser?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem was caused by a space in the data url I was using. It seems that the desktop browsers can handle a space properly, however the mobile browsers convert the space into a %20% character. jQuery mobile attempts to use a space, but the browser only remembers the altered character.

    EDIT:
    The jqm page has a data-url attribute that allows you to store multiple pages inside one html document.

    <html>
<head> ... </head>
<body>
<div data-role="page" data-url="page-one"> ... </div>
<div data-role="page" data-url="page two"> ... </div>
</body>
</html>

    The first pages can be loaded in a few ways…

    In a document

    <a href="#page-one">

    or through javascript

    $.mobile.changePage("#page-one");

    The problem I had was with the page with the data-url page two. On the desktop browsers the space was maintained, and the customized history control built into jqm continued to function as expected. but on the mobile browsers, the space turned into an escaped space, which the jqm history control did not recognize or track.

    • 0