Home/ Questions/Q 7921451
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-03T16:35:22+00:00

I’m running into a strange interaction between chrome and jquery mobile. The application flow

  • 0

I’m running into a strange interaction between chrome and jquery mobile. The application flow is straightforward:

  • Homepage / login screen. “Login” link is data-ajax="false" and rel="external" so all the fancy JQM AJAX stuff is disabled.
  • A series of 302s for the oauth dance which ends at /auth/facebook/callback
  • /auth/facebook/callback 302s to the real page /home which is a very simple Jquery-mobile page

On Chrome and Firefox the jquery mobile ‘ajax-loading’ spinner shows forever, with the actual page loaded in the DOM but not displaying. On Safari (desktop or mobile) the page displays properly.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem is coming from Facebook. When returning from oauth, they add a URL fragment #_=_ to your callback URL, which confuses JQM. As is typical for FB, this is documented as deliberate without justification but vague/incorrect instructions for how to deal with it. A bunch of discussion in this SO question. The best workaround I found is to insert this code to the top of your page before JQM has a chance to get confused:

    <script>
    // workaround Facebook oauth feature-bug
    if (window.location.hash == '#_=_') window.location.hash = '';
</script>
    • 0