Permalink
Browse files

Fix nested waiting-for-dom for initializePage.

Using dom-ready within dom-ready meant that initializePage went to the end of
the queue. That brought problems when other dom-ready code expected jQM to be
set up, capable of changing pages and so on. But because $.mobile.pageContainer
is also set in initializePage, changePage and others didn't work.
  • Loading branch information...
moll authored and johnbender committed Jul 25, 2011
1 parent cba80d9 commit 70bd1ba3711f93a7bf95dda3d4bc664d69f71a02
Showing with 3 additions and 3 deletions.
  1. +3 −3 js/jquery.mobile.init.js
View
@@ -123,9 +123,9 @@
// so if it's 1, use 0 from now on
$.mobile.defaultHomeScroll = ( !$.support.scrollTop || $(window).scrollTop() === 1 ) ? 0 : 1;
// dom-ready inits
if ( $.mobile.autoInitializePage ) {
$( $.mobile.initializePage );
//dom-ready inits
if( $.mobile.autoInitializePage ){
$.mobile.initializePage();
}
// window load event

0 comments on commit 70bd1ba

Please sign in to comment.