I'm having an interesting issue in jQuery Mobile (JQM).

You should know beforehand that I have a single-page template setup (separate pages) setting the following global configuration options, largely with the goal of turning off ajax and the jQM hash navigation system.

$.mobile.ajaxEnabled = "false";
$
.mobile.buttonMarkup.hoverDelay = "100";   
$
.mobile.defaultPageTransition = "none";    
$
.mobile.hashListeningEnabled = "false";
$
.mobile.pushStateEnabled = "false";
$
.mobile.loader.prototype.options.textVisible = true;
});

The Problem

I have a search result page, which obviously displays search results. Within the page is another form that allows the user to refine their search. Sometimes the user will decide that that they don't liked the refined results, and they'll want to click the back button to display their original results set. The problem is, on the JQM site, when the back button is clicked/tapped for this purpose, instead of being brought back to the original search results, the user is taken to the site's index page.

The interesting thing is, the page (minus the JQM-specific scripts/css) is identical to the static html version. That version behaves like it should.

Question:

Am I missing a global configuration option that would be helpful here? Is there anything else specific to JQM that could be causing this?

The Markup:

The page code is attached as it's too large to embed here.

Thanks so much for your help, everyone.