Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

iPhone - Page locks / Executes multiple transitions / loads random page (Beta3 - RC1?) #2585

dsyhre opened this Issue Oct 1, 2011 · 3 comments


None yet
4 participants

dsyhre commented Oct 1, 2011

I posted this issue on the jQuery Mobile forums: https://forum.jquery.com/topic/jqm-beta3-1-0-rc1-iphone-critical-bug

It has been experienced by multiple users who use the site (a company mobile intranet site for employees only) and forced us to rollback to beta2.

Our JQM linked image lists contain links to sub pages of our site. We have the rel="external" set on all of them to prevent the # sign being added into our URLS (and transistions),

When a user clicks one of these links, sometimes the following issue happens.

  1. He was taken to the page but unable to take any action at first.

The page contains one linked image list item at the top, going to an external site. Then an accordion with three sections, with one containing another linked list with external links (when I say external here I mean external websites and rel='external' attribute).
2. When the user tried clicking a section of the accordion, nothing happened.
3. He then tried clicking the top link, then another section of the accordion, and still nothing.
4. Then he said something similar to " the page then did some really weird, jerky transitions, like the ones you see when going to another page".
5. Suddenly after the strange behavior stopped he was taken to a sub page on our site, only this page that wasn't even linked on the page he was on in the first place.

We received reports of this happening to other user's as well on other pages and jQM sites within the company so we use beta2 for now.

Did RC1 fix this issue? Is anyone aware of this issue on the JQM team or elsewhere? I searched multiple forums, Google, and all I could find was a post here on github with script someone wrote that may fix it but I have not tested it yet, here it is for reference:

var ua = navigator.userAgent;

var checker = {iphone: ua.match(/iPhone/)};

if (checker.iphone){

$( document ).bind( "mobileinit", function() {

  $.mobile.pushStateEnabled = false;




@ghost ghost assigned jblas Oct 3, 2011


jblas commented Oct 10, 2011


It's really hard to figure out what your specific problem is without an actual example that demonstrates the problem. Reading through the forum post you referenced, the problem mentioned by @thydron is a known Safari bug which folks are getting bit by. It's being tracked in issue 2521:


Does turning off pushStateEnabled as you posted in the code snippet above, make the problems go away for you?

Cc: @johnbender @toddparker


toddparker commented Oct 20, 2011

@dsyhre - We still can't take a look at this without a clearer test case. Please provide that soon or we'll have to close this issue as cannot reproduce.


jaspermdegroot commented May 28, 2012

Closed as cannot reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment